Map the components, dependencies and environments that support the product. Assess whether the architecture fits its needs, remains maintainable and makes infrastructure risks visible.
All writing
Systems & Security
Architecture & Infrastructure
How systems are built and deployed.
Pillar 02
Definition
Technical areas
- Application architecture, service boundaries and dependencies
- Hosting, cloud infrastructure and environment configuration
- Deployment pipelines, build permissions and release processes
What an assessment could examine
These are examples to adapt to the system and its risks, rather than results from an assessment.
- Trace data and dependencies between application components, external services and storage to locate fragile coupling or single points of failure.
- Compare environment configuration and access permissions to identify drift or unnecessary privileges.
- Review how a change is built, verified, deployed and rolled back, including dependency and infrastructure updates.
Possible improvements
Findings might lead to changes such as these. Prioritise the changes supported by evidence and verify their effect.
- Clarify component responsibilities and remove unnecessary architectural complexity.
- Make environment configuration repeatable and reduce excessive infrastructure permissions.
- Improve dependency maintenance, release checks and rollback procedures, then verify a representative deployment.