Skip to content
Logo
  • Home
  • All Courses
  • Course Categories
    • CYBERSECURITY
    • ETHICAL HACKING
    • NETWORKING & SYSTEMS
    • DIGITAL FORENSICS
    • WEB DESIGN & DEVELOPMENT
    • PROGRAMMING & SCRIPTING
  • GRC & Consulting
  • About Us
  • Contact Us
Try for free
Logo
  • Home
  • All Courses
  • Course Categories
    • CYBERSECURITY
    • ETHICAL HACKING
    • NETWORKING & SYSTEMS
    • DIGITAL FORENSICS
    • WEB DESIGN & DEVELOPMENT
    • PROGRAMMING & SCRIPTING
  • GRC & Consulting
  • About Us
  • Contact Us

ISO 27001:2022 Annex A Controls Audit Checklist

  • Home
  • Uncategorized
  • Cybersecurity
  • ISO 27001:2022 Annex A Controls Audit Checklist
Cybersecurity

ISO 27001:2022 Annex A Controls Audit Checklist

  • June 27, 2026
  • Com 0

Published by Jackson Godwin |  jacksontechnology.com.ng  |  info@jacksontechnology.com.ng

How to use this checklist This checklist covers all 93 controls across the four Annex A categories of ISO 27001:2022. For each control, use the checkbox column to mark progress during your audit. The Status column can be updated with: Compliant | Partial | Non-Compliant | N/A. Sample findings are provided to illustrate what non-compliance looks like in practice. Use this as a gap analysis tool, internal audit aid, or client-facing deliverable.

STATUS LEGEND

✓  Compliant~  Partial✗  Non-CompliantN/A  Not Applicable
A.5Organizational Controls (A.5.1 – A.5.37)
✓ControlDescriptionSample FindingStatus
☐A.5.1Policies for Information SecurityPolicy not reviewed in 2+ years.—
☐A.5.2Information Security Roles & ResponsibilitiesIncident response roles not clearly defined.—
☐A.5.3Segregation of Duties (SoD)Users hold developer and admin privileges simultaneously.—
☐A.5.4Management ResponsibilitiesNo formal management oversight for security policies.—
☐A.5.5Contact with AuthoritiesNo procedure for reporting breaches to regulatory bodies.—
☐A.5.6Contact with Special Interest GroupsNo record of participation in security sharing forums.—
☐A.5.7Threat IntelligenceThreat intelligence not regularly collected or integrated.—
☐A.5.8Information Security in Project ManagementSecurity risks not assessed during new project planning.—
☐A.5.9Inventory of Information & Associated AssetsAsset inventory excludes cloud-based storage locations.—
☐A.5.10Acceptable Use of Information & AssetsNo tracking of employee compliance with AUP.—
☐A.5.11Return of AssetsFormer employees retain access to corporate laptops.—
☐A.5.12Classification of InformationCustomer financial data not classified by sensitivity.—
☐A.5.13Labeling of InformationConfidential files mislabeled, leading to unauthorized access.—
☐A.5.14Information TransferSensitive data transferred via unencrypted email.—
☐A.5.15Access ControlAccess permissions not reviewed; excessive privileges persist.—
☐A.5.16Identity ManagementInactive user accounts remain active, increasing risk.—
☐A.5.17Authentication InformationMFA not enforced for privileged accounts.—
☐A.5.18Access RightsFormer employees retain sensitive system access.—
☐A.5.19Information Security in Supplier RelationshipsVendor security assessments not conducted before onboarding.—
☐A.5.20Addressing IS in Supplier AgreementsSupplier contracts lack data protection clauses.—
☐A.5.21Managing IS in the ICT Supply ChainNo risk management process for third-party software vendors.—
☐A.5.22Monitoring, Review & Change Mgmt of Supplier ServicesThird-party security controls not audited in over a year.—
☐A.5.23Information Security for Cloud ServicesCloud data not encrypted at rest, violating policy.—
☐A.5.24Incident Management Planning & PreparationIncident response plan not tested in the last year.—
☐A.5.25Assessment & Decision on Information Security EventsNo formal process to categorize security events by impact.—
☐A.5.26Response to Information Security IncidentsIncident response delayed due to unclear escalation procedures.—
☐A.5.27Learning from Information Security IncidentsNo formal post-incident review process in place.—
☐A.5.28Collection of EvidenceEvidence collection procedures not followed, affecting forensics.—
☐A.5.29Information Security During DisruptionNo security controls tested during last BCP exercise.—
☐A.5.30ICT Readiness for Business ContinuityLast DR test failed due to outdated backup configurations.—
☐A.5.31Legal, Statutory, Regulatory & Contractual RequirementsNo documented process to monitor compliance with data laws.—
☐A.5.32Intellectual Property Rights (IPR)Software licenses not actively monitored.—
☐A.5.33Protection of RecordsFinancial records inadequately protected per regulatory requirements.—
☐A.5.34Privacy & Protection of PIISensitive PII stored without encryption.—
☐A.5.35Independent Review of Information SecurityLast independent security review conducted over two years ago.—
☐A.5.36Compliance with Policies, Rules & StandardsEmployees not regularly tested for policy adherence.—
☐A.5.37Documented Operating ProceduresCritical operating procedures are outdated and unavailable to staff.—
A.6People Controls (A.6.1 – A.6.8)
✓ControlDescriptionSample FindingStatus
☐A.6.1ScreeningNo formal background screening for contract employees.—
☐A.6.2Terms & Conditions of EmploymentEmployment contracts do not specify security obligations.—
☐A.6.3Information Security Awareness, Education & Training40% of employees did not complete annual security training.—
☐A.6.4Disciplinary ProcessNo disciplinary actions taken for repeated password-sharing.—
☐A.6.5Responsibilities After Termination or Change of EmploymentSome former employees retain access to applications post-exit.—
☐A.6.6Confidentiality / Non-Disclosure Agreements (NDAs)NDAs not consistently reviewed or renewed for sensitive roles.—
☐A.6.7Remote Working20% of remote employees not using an approved VPN.—
☐A.6.8Information Security Event ReportingEmployees unaware of reporting process; delays in breach detection.—
A.7Physical Controls (A.7.1 – A.7.14)
✓ControlDescriptionSample FindingStatus
☐A.7.1Physical Security PerimetersPerimeters not well-defined; unauthorized access to sensitive areas.—
☐A.7.2Physical EntryVisitors granted access to critical areas without authorization.—
☐A.7.3Securing Offices, Rooms & FacilitiesSecure room doors left unlocked during non-business hours.—
☐A.7.4Physical Security MonitoringSecurity cameras covering key areas non-functional for weeks.—
☐A.7.5Protecting Against Physical & Environmental ThreatsNo fire suppression system installed in the data center.—
☐A.7.6Working in Secure AreasStaff not consistently following badge identification policies.—
☐A.7.7Clear Desk & Clear ScreenSensitive documents left visible on desks after business hours.—
☐A.7.8Equipment Siting & ProtectionServer racks lack adequate physical security measures.—
☐A.7.9Security of Assets Off-PremisesLaptops taken off-site without encryption enabled.—
☐A.7.10Storage MediaOld hard drives not securely wiped before disposal.—
☐A.7.11Supporting UtilitiesNo backup power system for critical processing facilities.—
☐A.7.12Cabling SecurityExposed network cables increase risk of interception.—
☐A.7.13Equipment MaintenanceBiometric access controls not serviced in over a year.—
☐A.7.14Secure Disposal or Re-Use of EquipmentSensitive data not erased from devices before disposal.—
A.8Technological Controls (A.8.1 – A.8.34)
✓ControlDescriptionSample FindingStatus
☐A.8.1User Endpoint DevicesMany endpoint devices lack full disk encryption.—
☐A.8.2Privileged Access RightsPrivileged accounts not reviewed in over six months.—
☐A.8.3Information Access RestrictionEmployees retain access to sensitive data after role changes.—
☐A.8.4Access to Source CodeDevelopers have direct write access to production repositories.—
☐A.8.5Secure AuthenticationMFA not enabled for all privileged accounts.—
☐A.8.6Capacity ManagementCritical applications running at 90% capacity; availability at risk.—
☐A.8.7Protection Against MalwareMany workstations running outdated anti-malware software.—
☐A.8.8Management of Technical VulnerabilitiesCritical vulnerabilities unpatched for over 90 days.—
☐A.8.9Configuration ManagementProduction server configurations do not comply with baselines.—
☐A.8.10Information DeletionSensitive data not fully erased before decommissioning devices.—
☐A.8.11Data MaskingProduction data used in test environments without anonymization.—
☐A.8.12Data Leakage PreventionDLP rules for email exfiltration are not enforced.—
☐A.8.13Information BackupBackups not regularly tested for recoverability.—
☐A.8.14Redundancy of Information Processing FacilitiesNo secondary data center exists for critical redundancy.—
☐A.8.15LoggingSecurity logging not enabled for some critical systems.—
☐A.8.16Monitoring ActivitiesNo centralized logging system to detect security anomalies.—
☐A.8.17Clock SynchronizationSeveral systems show time discrepancies greater than five minutes.—
☐A.8.18Use of Privileged Utility ProgramsPrivileged users executed system commands without logging.—
☐A.8.19Installation of Software on Operational SystemsUnauthorized software found running on production systems.—
☐A.8.20Network SecurityNetwork firewalls have outdated firmware exposing them to threats.—
☐A.8.21Security of Network ServicesThird-party network services not assessed for security compliance.—
☐A.8.22Segregation of NetworksPayment processing systems not isolated from general user networks.—
☐A.8.23Web FilteringUnrestricted access to social media and file-sharing sites.—
☐A.8.24Use of CryptographyEncryption keys not rotated regularly.—
☐A.8.25Secure Development LifecycleDevelopers not trained on secure coding practices.—
☐A.8.26Application Security RequirementsSecurity requirements not considered before purchasing third-party software.—
☐A.8.27Secure System Architecture & Engineering PrinciplesArchitecture does not follow least-privilege principle.—
☐A.8.28Secure CodingDevelopers not consistently following secure coding standards.—
☐A.8.29Security Testing in Development & AcceptanceCritical applications deployed without undergoing security testing.—
☐A.8.30Outsourced DevelopmentOutsourced development lacks security oversight.—
☐A.8.31Separation of Dev, Test & Production EnvironmentsTesting and production environments not properly isolated.—
☐A.8.32Change ManagementUnauthorized system changes made without formal approval.—
☐A.8.33Test InformationSensitive production data used in testing without anonymization.—
☐A.8.34Protection of IS During Audit TestingAudit testing performed on live production systems without safeguards.—
 Audit Summary Score Total Controls: 93   |   Compliant: ___   |   Partial: ___   |   Non-Compliant: ___   |   N/A: ___ Compliance Score: ____%   |   Audit Date: ____________   |   Auditor: ______________________

Jackson Technology  |  Cybersecurity & Data Protection Consulting  |  Abuja, Nigeria

This checklist is provided for informational and audit preparation purposes only. For certification audits, engage an accredited ISO 27001 certification body.

Download ISO 27001 Checklist Here file↗

Share on:
The 2026 Pathway to Getting Hired in Cybersecurity Canada  •  United Kingdom  •  United States
The 2026 Canadian Compliance Shift: The Secret Weapon Businesses Cannot Ignore

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Categories

  • Cybersecurity
  • VAPT LAB
https://jacksontechnology.com.ng/wp-content/uploads/2026/08/8632594-Uhd-2160-3840-25Fps.mp4
© 2026 - EduBlink. All Rights Reserved. Proudly powered by DevsBlink
Logo
Sign inSign up

Sign in

Don’t have an account? Sign up
Lost your password?

Sign up

Already have an account? Sign in