Secure Requirements

KR03 Lead: IT Innovation Centre

Security requirements identification tool.

KR03 allows models of end-to-end applications to be created, and security threats and compliance issues affecting that application to be automatically identified through machine-based reasoning techniques. The exploitation of this KR is tightly coupled with KR01 and KR02.

Market assessment:

Several tools similar to this one exist in the market, such as the Microsoft SDL 48 or ThreatModeler by Myappsecurity49 as well as open source alternatives such as the student-developed web tool SeaSponge50. These tools comply with the security-by-design approach that will be used in the context of SHiELD. However, these tools differ from SHiELD in that they do not use machine-based reasoning techniques to identify sensitive data, nor they take into consideration regulatory aspects of such sensitive data as health-related data. According to PwC’s Global State of Information Security Survey 2014 executives are generally increasing security budgets to fund security safeguards, processes, and strategies. A range of tools now exist to help analysts identify security threats but most (e.g. eBIOS, OCTAVE or MEHARI) provide only document schema or checklists to assist manual analysis. Software tools such as vRISK and Microsoft Threat Modelling Tool are quite similar, helping users capture information related to their system, providing checklists which may be specific to certain system features, but not a comprehensive automated threat identification and analysis procedure. Even AURIUM, which is based on the SBA security ontology, uses encoded knowledge to prompt rather than automate.

Route to the market:

The threat modeller tool can be deployed as an Eclipse-built in tool or as a SaaS. Freemium. Certain core functionalities will be offered for free to establish the SHIELD tool w.r.t. existing free or low cost tools like Microsoft SDL. Analysis of compliance aspects will be made available on commercial terms, by licensing the relevant knowledge bases (from KR01) to commercialization partners such as AIMES. The exact free functionalities need to be further analysed.

Stakeholders:

Developers and operators, Healthcare providers, ICT providers for the health sector, Public sector.

Success criteria:

Modelling tool allows threats and compliance requirements to be identified, and security measures to address them specified at least an order of magnitude faster than by using conventional methods. The analysis should also be easy to repeat should new threats emerge or regulations change.

« Back to tools