6 docs tagged with "ameaças"

Method used to validate claims of traceability, maturity and mitigated threats in the SbD-ToE manual

How to replace the manual threat → requirement mapping using platforms such as IriusRisk, while maintaining traceability with Chapter 2

Technical and process indicators for assessing the coverage, quality and integration of threat modelling in the development cycle, with thresholds by risk level and mapping to the cross-cutting SbD-ToE governance dimensions.

Mapping known threats is an essential mechanism for validating the risk analysis, ensuring that the identified risks reflect real, plausible and documented attack vectors.

Organisational policy that defines the mandatory nature, methodology, execution triggers, formal approval requirements, traceability and management of threat modelling artefacts throughout the lifecycle of applications classified L2 and L3.

Canonical catalogue of threat modelling requirements (THR-001 to THR-007), with applicability by risk level and acceptance criteria for threat identification, formal disposition, requirement derivation and methodological traceability.