Security Architecture

Think in threats and trust boundaries rather than in security products.

3Questions
16Flashcards
18Terms
1/20Topics covered
The syllabus

20 topics in this area.

Each topic is the unit content is filed against. Topics with nothing in them yet are shown too — they are the honest edge of the curriculum rather than a gap being hidden.

Security Architecture

General material on securing an architecture.

3 quiz 16 cards 18 terms

Authentication

Establishing who a principal is, and how strong that claim needs to be.

No content yet

Authorization

RBAC, ABAC and ReBAC, and centralising the decision but not the enforcement.

No content yet

OAuth 2.0 & OIDC

Delegated authorisation, and the identity layer that makes login safe.

No content yet

Tokens & JWTs

Stateless validation, revocation, and pinning the algorithm.

No content yet

Identity & Access Management

Workload identity, roles, permission boundaries and usage-based review.

No content yet

Secrets Management

Runtime injection, dynamic credentials and rotation applications survive.

No content yet

Encryption

At rest, in transit, and at the application layer — three different threats.

No content yet

Key Management

Rotation, separation of duty, envelope encryption and crypto-shredding.

No content yet

Zero Trust

No implicit trust from network position; authorise every request.

No content yet

Threat Modelling

Walking trust boundaries with STRIDE before anything is built.

No content yet

OWASP Risks

The recurring web and API risk classes, several of which are design flaws.

No content yet

Secure API Design

Object-level authorisation, input validation and safe error responses.

No content yet

Supply Chain Security

Dependencies, SBOMs, build provenance and artefact signing.

No content yet

Network Security

Segmentation, egress control and limiting lateral movement.

No content yet

Auditability

Tamper-evident, attributed records that survive async boundaries.

No content yet

Compliance Frameworks

SOC 2, ISO 27001, PCI DSS — scope as an architectural lever.

No content yet

Privacy Engineering

Minimisation, purpose limitation, and erasure that is implementable.

No content yet

Data Classification

Knowing which fields are regulated, because every control depends on it.

No content yet

Security Incident Response

Detection, scoping, containment and notification clocks.

No content yet