Threat modelling is used in support of application development.
Ensure the software design meets all security requirements and addresses identified risks by conducting design reviews. Engage qualified personnel who were not involved in the original design or use automated processes in the toolchain to verify security compliance. Assess the design against risk models, address any identified issues, make adjustments to the design or risk responses as needed, and document the findings of each review. This review process helps reinforce secure design and mitigates risks early in development.
Verify that the solution architecture systematically addresses all identified security and compliance requirements. For each interface within the application, review the list of security and compliance requirements and evaluate the architecture to confirm their integration. Conduct interaction or data flow analyses to ensure comprehensive coverage of these requirements across different components, and provide detailed insights into the design-level features that fulfill each requirement. This analysis should encompass both internal interfaces, such as those between tiers, and external interfaces, including those forming the application's attack surface. Validate and document key design decisions, especially when they diverge from established shared security solutions within the organization. Continuously update findings throughout the development lifecycle, reflecting any design changes or newly identified gaps. Highlight and document requirements that remain unmet or ambiguously addressed during the design stage as formal assessment findings. This iterative review process ensures that the architecture evolves securely, minimizing risks and maintaining compliance with organizational standards.
| ID | Operation | Description | Phase | Agent |
|---|---|---|---|---|
| SSS-02-03-02-01-01 | Map security and compliance requirements to architecture | Review the solution architecture and map all security and compliance requirements to the corresponding design components and interfaces. | Preparation | Architects, Security team, Compliance officers |
| SSS-02-03-02-01-02 | Perform interface-level analysis | Analyze internal and external interfaces for compliance with security requirements. Evaluate data flows and interactions across components to ensure alignment. | Preparation | Architects, Security team |
| SSS-02-03-02-01-03 | Validate key design decisions | Identify and review significant design decisions, especially deviations from organizational security standards, ensuring their security implications are well understood. | Development | Architects, Development leads |
| SSS-02-03-02-01-04 | Document design features addressing requirements | Elaborate and document how the architectural design meets each security and compliance requirement, highlighting key features and mechanisms. | Development | Architects, Compliance officers |
| SSS-02-03-02-01-05 | Update findings during development cycles | Periodically review and update the analysis to reflect changes made during development. Record any gaps or unaddressed requirements for further assessment. | Deployment | Architects, Security team |
| Industry framework | Academic work | Real-world case |
|---|---|---|
|
Information Security Manual (ISM-1238) NIST Secure Software Development Framework (PW.2.1) OWASP SAMM: Software Assurance Maturity Model (V-AA-2-A) |