Dashboard

ISO 27001:2022 Annex A Assessment

Stage-1 Readiness: Not Ready (0% composite)

Composite below 50%. Significant implementation work required before pursuing ISO 27001 certification.

Disclaimer: This assessment is an internal tracking aid only. ISO 27001 certification requires a formal Stage-1 + Stage-2 audit conducted by a JAS-ANZ accredited certification body.

Overall Progress
0%
x
0 Implemented0 In Progress93 Not Started0 N/A
Per-Theme Maturity
A.5Organizational
0%Basic
x
A.6People
0%Basic
x
A.7Physical
0%Basic
x
A.8Technological
0%Basic
x
Theme Maturity Radar
Status Distribution by Theme
Overall Status Mix
Top Priority Gaps (by criticality)
1
A.5.1Policies for information security

Define, approve at management level, publish, and communicate a set of information security policies. Policies must be reviewed at planned intervals and when significant changes occur. Ensure each policy has an owner and a review date; store approved versions in a document management system accessible to all staff.

Not StartedHigh criticality
2
A.5.2Information security roles and responsibilities

Assign and document information security roles (CISO, data owner, system custodian, end-user) in job descriptions and an RACI matrix. Every information asset must have a named owner responsible for its protection. Confirm roles are communicated during onboarding and re-confirmed annually.

Not StartedHigh criticality
3
A.5.9Inventory of information and other associated assets

Maintain a comprehensive asset register covering hardware, software, data assets, and services. Each asset entry should record: asset ID, description, owner, classification, location, and disposal method. Review and reconcile the asset register at least annually and after significant infrastructure changes.

Not StartedHigh criticality
4
A.5.12Classification of information

Define an information classification scheme (e.g., Public / Internal / Confidential / Restricted) with clear criteria for each level. Document which business data types map to which classification. Provide decision-tree guidance to help staff classify new documents correctly at creation.

Not StartedHigh criticality
5
A.5.15Access control

Establish and document an access control policy based on need-to-know and least privilege. Define access provisioning, review, and revocation processes. Conduct access reviews at least semi-annually for privileged accounts and annually for standard accounts. The policy should cover logical, physical, and remote access.

Not StartedHigh criticality
6
A.5.16Identity management

Maintain a full lifecycle management process for all identities (employees, contractors, service accounts, machine identities). Every identity must be uniquely identifiable (no shared accounts). Implement a joiner-mover-leaver process integrated with HR; automate deprovisioning within 24 hours of termination.

Not StartedHigh criticality
7
A.5.17Authentication information

Define password/passphrase policies (minimum length, complexity, no reuse, no default credentials). Require MFA for all remote access and privileged accounts. Provide a secure password manager to all staff. Audit authentication configuration against policy quarterly. Do not allow passwords to be transmitted in plaintext.

Not StartedHigh criticality
8
A.5.18Access rights

Implement a formal request, approval, provisioning, and review process for all access rights. Access to sensitive systems requires documented manager approval. Maintain a register of privileged access grants. Conduct quarterly reviews of privileged rights and annual reviews of all other rights; document and action findings.

Not StartedHigh criticality
9
A.5.24Information security incident management planning and preparation

Define and document an incident management process covering detection, triage, containment, eradication, recovery, and post-incident review. Assign an Incident Response Team (IRT) with documented roles. Conduct at least one tabletop exercise per year. Ensure the process includes escalation paths and regulatory notification obligations (CERT-In 6-hour rule, DPDP obligations).

Not StartedHigh criticality
10
A.5.26Response to information security incidents

Execute incident response according to documented procedures, ensuring containment actions are taken swiftly and evidence is preserved forensically where required. Maintain an incident log with timeline, actions taken, decisions made, and personnel involved. Notify relevant stakeholders and authorities within required timeframes.

Not StartedHigh criticality
11
A.5.31Legal, statutory, regulatory and contractual requirements

Identify and document all legal, statutory, regulatory (IT Act 2000, DPDP Act 2023, CERT-In directions, sector regulators such as RBI/SEBI/IRDAI), and contractual requirements relevant to information security. Assign ownership for each compliance obligation. Review the register at least annually and when regulations change.

Not StartedHigh criticality
12
A.5.34Privacy and protection of personally identifiable information

Establish and maintain a privacy program aligned to applicable privacy regulations (DPDP Act 2023 in India). Define roles (Data Fiduciary, Data Principal), data processing purposes, consent mechanisms, and data subject rights handling. Maintain a Record of Processing Activities (RoPA). Conduct Data Protection Impact Assessments (DPIAs) for high-risk processing.

Not StartedHigh criticality
13
A.6.3Information security awareness, education and training

Deliver mandatory information security awareness training to all staff at onboarding and annually thereafter. Training must cover phishing recognition, password hygiene, data classification, incident reporting, and relevant policies. Track completion rates and maintain training records. Conduct phishing simulation exercises at least twice per year and use results to target further training.

Not StartedHigh criticality
14
A.6.8Information security event reporting

Establish and communicate a clear, easy-to-use channel for staff to report security events (suspicious emails, lost devices, unauthorized access). Define what constitutes a reportable event. Set a target reporting time (e.g., within 2 hours of discovery). Provide a no-blame culture to encourage reporting. Measure the number of events reported as a security culture metric.

Not StartedHigh criticality
15
A.8.1User endpoint devices

Establish and enforce security configuration standards for all user endpoint devices (laptops, desktops, mobile phones, tablets). Minimum requirements: full-disk encryption, EDR/antivirus, MDM enrollment, OS and software patching within defined SLAs, and screen lock. Maintain a device inventory and compliance dashboard. Block unmanaged devices from accessing corporate resources.

Not StartedHigh criticality