Classification of information

What is Classification of information?

Classification of information is the systematic process of categorising data into groups based on its legal sensitivity and business value. The primary implementation requirement involves formalising a tiered labelling scheme under Annex A 5.12, providing the business benefit of risk-aligned security resource allocation and protected organisational intellectual property.

What is Classification of information?

The process of putting information into groups based on how sensitive it is. This helps an organisation know how much protection to give each piece of data. It ensures that valuable or private information is kept safe, while public information is easy to share.

Examples

  • Public: A company’s website or a press release. This information is meant for everyone to see.
  • Internal: Employee handbooks or meeting notes. This information is for staff only and shouldn’t be shared outside the company.
  • Confidential: Customer records or financial reports. This is very private data that, if lost, could cause great harm to the company or its clients.

Context

Classifying information is a key step in keeping it secure. It’s like putting different valuables into different kinds of safes. You wouldn’t put a common coin in a high-tech bank vault, just as you wouldn’t leave a precious gem in an open box. This practice helps a business use its security resources wisely. It also makes sure that everyone knows how to handle different types of data correctly.

How to implement Classification of information

Implementing the classification of information is a core requirement of ISO 27001 Annex A 5.10, 5.12, and 5.13. As a Lead Auditor, I have seen that failure to correctly categorise data leads to either expensive over-protection or catastrophic under-protection of assets. Follow this 10-step roadmap to formalise your data hierarchy, resulting in a risk-aligned security posture that satisfies mandatory compliance and protects your organisation’s most sensitive intellectual property.

1. Provision an Information Asset Register

  • 1. Provision an Information Asset Register: Identify all data, hardware, and software assets within the ISMS boundary, resulting in a complete inventory that serves as the foundation for all subsequent classification activities.

2. Formalise Classification Levels and Definitions

  • 2. Formalise Classification Levels and Definitions: Formalise a tiered classification scheme: Define specific levels such as Public, Internal, Confidential, and Highly Restricted, resulting in a standardised language for data sensitivity across the entire organisation.

3. Provision Data Labeling and Marking Standards

  • 3. Provision Data Labeling and Marking Standards: Provision technical metadata and visual marking standards: Establish how classification should be applied to digital files and physical documents, resulting in clear, recognisable indicators of how data must be handled.

4. Document Handling Rules of Engagement (ROE)

  • 4. Document Handling Rules of Engagement (ROE): Document the Rules of Engagement for each classification level: Define specific storage, transmission, and destruction requirements for each tier, resulting in enforceable technical procedures that prevent data leakage.

5. Formalise Asset Ownership and Responsibility

  • 5. Formalise Asset Ownership and Responsibility: Formalise the role of the Information Asset Owner: Assign accountability for classification accuracy to specific process owners, resulting in accurate data categorisation based on actual business value.

6. Provision Technical DLP and Tagging Tools

  • 6. Provision Technical DLP and Tagging Tools: Provision Data Loss Prevention (DLP) and automated tagging tools: Deploy software to identify and label sensitive data at rest and in transit, resulting in the technical enforcement of classification policies without manual error.

7. Implement Identity and Access Management (IAM) Roles

  • 7. Implement Identity and Access Management (IAM) Roles: Provision granular IAM roles based on classification levels: Map system access rights directly to the sensitivity of the information stored, resulting in the strict enforcement of the Principle of Least Privilege.

8. Enforce Multi-Factor Authentication (MFA) for Sensitive Tiers

  • 8. Enforce Multi-Factor Authentication (MFA) for Sensitive Tiers: Enforce MFA for all access to Confidential and Restricted data: Mandate strong authentication for the system boundaries where sensitive information resides, resulting in a hardened perimeter for your most critical assets.

9. Audit Classification Accuracy and Compliance

  • 9. Audit Classification Accuracy and Compliance: Audit the effectiveness of classification controls: Execute regular spot checks and technical scans to verify that data is correctly tagged, resulting in the identification of misclassified assets before an official audit.

10. Revoke Access and Sunset Redundant Data

  • 10. Revoke Access and Sunset Redundant Data: Revoke legacy access permissions and securely destroy redundant data: Regularly purge data that is no longer required according to its classification retention period, resulting in a reduced organisational attack surface.

Classification of information FAQ

What is classification of information in ISO 27001?

Classification of information is the formal process of categorising data based on its legal requirements, value, and sensitivity to unauthorised disclosure or modification. Under ISO 27001 Annex A 5.10, 100% of organisational information must be classified to ensure that security efforts are prioritised toward protecting the most critical assets, thereby reducing unnecessary control overhead by up to 30%.

What are the common ISO 27001 information classification levels?

While ISO 27001 does not mandate specific names, organisations typically adopt a four-tier modular structure:

  • Public: Information intended for general disclosure with 0% confidentiality risk.
  • Internal: General business data that is not sensitive but not for public release.
  • Confidential: Sensitive data such as PII or commercial contracts requiring restricted access.
  • Highly Restricted: Critical intellectual property or board-level data where a breach would cause catastrophic damage.

How does information classification impact access control?

Information classification dictates the technical access requirements, ensuring the Principle of Least Privilege is enforced. For data classified as Confidential or above, ISO 27001 requires robust Identity and Access Management (IAM) and Multi-Factor Authentication (MFA). Statistics show that correctly classified data environments are 50% less likely to suffer from internal data leakage.

Who is responsible for classifying information within an organisation?

The Information Asset Owner is primarily responsible for the classification of information under their remit. While the CISO provides the framework, the asset owner understands the business value and impact of the data. Ensuring 100% accountability through an Information Asset Register is a fundamental requirement for passing an ISO 27001 certification audit.

How often should information classification be reviewed?

Information classification must be reviewed at least annually or whenever significant technical or organisational changes occur. Continuous monitoring ensures that data which was once Highly Restricted but is now obsolete is downgraded or securely destroyed. Regular reviews prevent “security debt” and ensure compliance with approximately 80% of global data privacy regulations.

Relevant ISO 27001 Controls

The following controls from the ISO/IEC 27001:2022 standard are related to classification of information:

Stuart and Fay High Table

About the author

Stuart Barker
🎓 MSc Security 🛡️ Lead Auditor 30+ Years Exp 🏢 Ex-GE Leader

Stuart Barker

ISO 27001 Ninja

Stuart Barker is a veteran practitioner with over 30 years of experience in systems security and risk management. Holding an MSc in Software and Systems Security, he combines academic rigor with extensive operational experience, including a decade leading Data Governance for General Electric (GE).

As a qualified ISO 27001 Lead Auditor, Stuart possesses distinct insight into the specific evidence standards required by certification bodies. His toolkits represent an auditor-verified methodology designed to minimise operational friction while guaranteeing compliance.

Shopping Basket
Scroll to Top