Prof. Dr. Larry AdamsAcademic, Author & Researcher
Cyber Security — Level 7 · 12 slides

Presentation · 12 slides

Cyber Security — Level 7

Risk-Led Security Strategy, Architecture, Assurance, Incident Response and Resilience

Prof. Dr. Larry Adams

A Level 7 teaching deck on Cyber Security: Risk-Led Security Strategy, Architecture, Assurance, Incident Response and Resilience.

Free to view online and to download for teaching, with acknowledgement of the author. To reproduce or adapt any part of a deck, please request permission through the contact page beforehand.

  1. Cyber Security — Level 7

    UKVAA • ADVANCED STUDY SERIES

    Level 7 Cyber Security

    Risk-Led Security Strategy, Architecture, Assurance, Incident Response and Resilience

    Level 7 | Strategic and critical application

    Teaching presentation • First edition • 2026

    01
  2. Learning outcomes

    • Evaluate cyber risk in organisational and sector context.
    • Design layered security architecture and governance controls.
    • Assess identity, network, endpoint, application, cloud and data protection.
    • Develop incident response, recovery, assurance and third-party risk practices.
    • Communicate risk in business terms and prioritise proportionate investment.
    02
  3. Cyber risk and threat landscape

    • Security protects confidentiality, integrity and availability while supporting safety and mission delivery.
    • Risk depends on threat, exposure, vulnerabilities, impact and existing controls.
    • Common threats include phishing, credential theft, ransomware, exploitation, insider misuse and supply-chain compromise.
    • Model attack paths from initial access through privilege escalation, lateral movement and impact.
    • Prioritise by exploitability, asset criticality and likely consequence—not raw vulnerability counts alone.
    03
  4. Governance, architecture and zero trust

    • Define policies, roles, risk ownership, exceptions, escalation and board reporting.
    • Maintain asset inventory and classify systems and information by sensitivity and impact.
    • Use segmentation, secure defaults, least privilege and explicit trust boundaries.
    • Apply threat modelling to identify abuse cases and high-value targets.
    • A certificate or compliance result is evidence for a defined scope, not proof of zero risk.
    04
  5. Identity and access management

    • Use unique identities and strong authentication; prioritise phishing-resistant MFA for high-risk access.
    • Apply least privilege, role separation, just-in-time elevation and periodic access reviews.
    • Manage joiner/mover/leaver processes and service accounts consistently.
    • Protect secrets and recovery paths; monitor unusual authentication and privilege changes.
    • Cover cloud consoles, endpoints, applications, APIs and third parties.
    05
  6. Network, endpoint, cloud and software security

    • Segment critical systems and restrict unnecessary east-west traffic.
    • Harden endpoints, patch systems, control local admin rights and use endpoint detection.
    • Secure cloud configuration, logging, encryption and shared-responsibility ownership.
    • Integrate threat modelling, code review, dependency checks and security testing into development.
    • Prioritise vulnerabilities by exploitability, exposure, asset criticality and compensating controls.
    06
  7. Cryptography and data protection

    • Classify data and define retention, access, sharing, backup and destruction requirements.
    • Use reviewed cryptographic libraries and approved configurations; never invent algorithms.
    • Protect keys through lifecycle management, access separation, rotation and recovery.
    • Encryption does not replace access controls, monitoring or secure endpoints.
    • Apply local privacy, data residency and lawful processing requirements.
    07
  8. Monitoring and incident response

    • Collect useful, time-synchronised logs from identity, endpoint, network, cloud and critical applications.
    • Define detection use cases based on realistic threats and business-critical assets.
    • Prepare severity criteria, evidence handling, contact lists and legal/privacy escalation.
    • Contain safely, preserve evidence, eradicate root causes and recover in a controlled manner.
    • Run post-incident reviews focused on systemic causes, control gaps and measurable action.
    08
  9. Continuity, supply chain and human factors

    • Set recovery time and recovery point objectives for critical services.
    • Keep protected, tested backups and separate recovery credentials from production paths.
    • Map suppliers, managed service providers, software dependencies and data-sharing relationships.
    • Contract for security obligations, notification, subcontractors, audit evidence and exit support.
    • Make reporting easy and non-punitive; avoid blaming individuals for unsafe system design.
    09
  10. AI, metrics and security strategy workshop

    • Use AI for analysis cautiously; test false positives, data exposure and automation bias.
    • Protect model endpoints, prompts, retrieval sources, credentials and tool permissions.
    • Track asset coverage, MFA coverage, remediation age, recovery tests and response time.
    • Build a 12-month roadmap with owners, budget, milestones and risk-reduction measures.
    • Run a tabletop incident covering detection, containment, communication and recovery decisions.
    10
  11. End-text references and further reading (1)

    • CIS (2021). CIS Critical Security Controls v8.
    • ENISA. ENISA Threat Landscape reports; consult the latest edition.
    • ISO 22301:2019; ISO/IEC 27001:2022; ISO/IEC 27004; ISO/IEC 27035; ISO/IEC 27036.
    • MITRE. ATT&CK knowledge base.
    • NIST (2012). SP 800-61 Rev. 2 Computer Security Incident Handling Guide.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    11
  12. End-text references and further reading (2)

    • NIST (2020). SP 800-53 Rev. 5; NIST SP 800-207 Zero Trust Architecture.
    • NIST (2022). SP 800-63B Digital Identity Guidelines; NIST SP 800-161 Rev. 1 Supply Chain Risk Management.
    • NIST (2022). SP 800-218 Secure Software Development Framework; NIST (2023). AI Risk Management Framework.
    • NIST (2024). Cybersecurity Framework 2.0 and post-quantum cryptography publications.
    • OWASP Foundation. OWASP Top 10 and Application Security Verification Standard; applicable local cyber and privacy law.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    12
01 / 12