ISO 27001:2022 Annex A 6.2 – Terms and Conditions of Employment Explained

Information security responsibilities start before day one.

Annex A 6.2 exists to ensure organisations clearly define information security responsibilities within the terms and conditions of employment, so expectations are understood, agreed, and enforceable from the outset.

This control anchors information security obligations in contractual reality, not policy assumption.

ISO 27001

Quick Guide: Annex A 6.2 at a Glance

Annex A 6.2 of ISO 27001:2022 focuses on information security responsibilities within employment terms.

At a practical level, this means:

  • Defining information security responsibilities contractually
  • Making confidentiality obligations explicit
  • Referencing applicable policies and standards
  • Clarifying consequences of non-compliance
  • Ensuring obligations apply before access is granted

The control does not prescribe contract wording or legal structure. It expects organisations to ensure information security responsibilities are formally agreed and legally enforceable.

In-Depth Guide to Annex A 6.2

What Is Annex A 6.2 and Why Does It Matter?

Annex A 6.2 of ISO 27001:2022 focuses on information security responsibilities within employment terms.

At a practical level, this means:

  • Defining information security responsibilities contractually
  • Making confidentiality obligations explicit
  • Referencing applicable policies and standards
  • Clarifying consequences of non-compliance
  • Ensuring obligations apply before access is granted

The control does not prescribe contract wording or legal structure. It expects organisations to ensure information security responsibilities are formally agreed and legally enforceable.

How to Implement Annex A 6.2 Effectively

A pragmatic approach to Annex A 6.2 typically includes the following elements.

1. Define Information Security Responsibilities in Employment Terms

Employment terms should make clear that individuals are responsible for:

  • Protecting organisational information and assets
  • Following information security policies and procedures
  • Using systems and information appropriately

This establishes security as a core duty, not a side obligation.

2. Address Confidentiality Obligations Explicitly

Where individuals may access confidential or sensitive information, terms often address:

  • Confidentiality during employment
  • Ongoing confidentiality after employment ends
  • Restrictions on disclosure or misuse

Clarity here reduces both insider risk and legal ambiguity.

3. Reference Applicable Policies and Standards

Contracts commonly reference:

  • Information security policies
  • Acceptable use rules
  • Topic-specific security standards

This avoids duplicating content while ensuring contractual linkage.

4. Clarify Legal and Regulatory Responsibilities

Employment terms may outline responsibilities relating to:

  • Data protection and privacy law
  • Intellectual property
  • Regulatory or sector-specific obligations

This reinforces that legal compliance is part of the individual’s role.

5. Define Consequences of Non-Compliance

Annex A 6.2 supports transparency around:

  • Disciplinary action
  • Contractual consequences
  • Legal or regulatory implications

Consequences should be clear, lawful, and proportionate.

6. Apply Terms Before Access Is Granted

Information security obligations should be agreed:

  • Before system or information access is provided
  • Before sensitive duties are performed

Access should not be granted on the basis of unsigned or incomplete terms.

7. Review Terms When Roles Change

Where responsibilities change significantly, organisations may:

  • Review employment terms
  • Update confidentiality or security clauses

This ensures obligations remain aligned with access and risk.

Practical Considerations

Annex A 6.2 does not require:

  • Lengthy or complex contracts
  • Legal language in security policies
  • Rewriting contracts for minor policy changes

It does require organisations to:

  • Ensure security responsibilities are explicit
  • Avoid relying solely on policy acknowledgment
  • Align contractual terms with actual security expectations

Contracts define boundaries.
Policies explain how to operate within them.

Common Challenges and How to Overcome Them

  • Relying on policies without contractual backing
  • Reference information security responsibilities in employment terms
  • Unclear confidentiality obligations
  • Make confidentiality explicit and enforceable
  • Granting access before terms are agreed
  • Complete contractual steps before onboarding access
  • Outdated employment terms
  • Review when roles or risks change

Most disputes arise from ambiguity, not intent.

Final Recommendations

Annex A 6.2 is about setting expectations that hold up under scrutiny.

When information security is embedded in employment terms:

  • Responsibilities are clear
  • Enforcement is defensible
  • Insider risk is reduced
  • Legal and regulatory exposure is better controlled

Security awareness can be forgotten.
Contractual responsibility is harder to ignore.

That is exactly what Annex A 6.2 is designed to achieve.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls