Annex A People and Physical Controls: Implementation and Evidence in Practice

ISO 27001:2022 Annex A people (6.1–6.8) and physical controls (7.1–7.14): implementation, evidence and field mistakes from hiring to leaving and from the front door to disk destruction.
Technical summary
Technology
ISO/IEC 27001:2022 Annex A, ISO/IEC 27002:2022, DIN 66399, KVKK
Topic
Implementing and evidencing human resources and physical security controls
Level
Intermediate
Prerequisites
  • A list of in-scope locations and secure areas
  • Defined HR processes (hiring, leaving)
In this article8 sections

If a leaver’s badge still opens the server room door three weeks later, it no longer matters how tight the firewall rule set is. Annex A’s people (6.1–6.8) and physical (7.1–7.14) themes contain 22 controls in total, and they’re areas the IT team can’t close on its own: HR, administration, facility management and legal have to work together. This guide follows the controls from an employee’s hiring to leaving, and from information entering the building to media being destroyed; it gives differences by location type and the evidence to present in the audit in tables.

Human resources controls: from hiring to leaving

The people theme consists of eight controls and follows the employee lifecycle:

  1. 6.1 Screening: Background verification before hiring. The scope must be proportionate to the classification of information the role accesses and the risks. In Türkiye, this verification is done within the limits of KVKK and employment law: confirming the diploma, certificates and references declared by the candidate is typical practice; if additional verification is to be done for sensitive roles, the legal basis and candidate notice must be settled in advance.
  2. 6.2 Terms and conditions of employment: Information security responsibilities in the employment contract or its annexes; obligations that continue after leaving.
  3. 6.3 Awareness, education and training: Induction on joining, periodic awareness and role-based training (separate content for managers, developers and IT administrators).
  4. 6.4 Disciplinary process: A process announced to employees in advance, applied to policy violations.
  5. 6.5 Responsibilities after termination or change of employment: Defining and reminding the person of confidentiality and other obligations that remain valid after leaving or changing roles. Removing old access rights is the subject of 5.18 in the organizational theme.
  6. 6.6 Confidentiality agreements: For employees, interns, consultants and supplier staff.
  7. 6.7 Remote working: Rules for accessing information outside the office.
  8. 6.8 Information security event reporting: How and where an employee reports something suspicious.

The most fragile point of this theme is the leaving process. The gap between the leaving date in HR and the account closure date in IT is the topic most often sampled in audits. The auditor asks for an HR list, asks for records of accounts being disabled from the directory service and puts the two side by side. If an open account turns up, that’s it. Turn the leaver form into a single checklist signed separately by HR, IT and administration; this list evidences 6.5, 5.11 and 5.18 together: disabling accounts (5.18), revoking remote access and MFA devices, returning the laptop, badge and keys (return control is 5.11 in the organizational theme) and changing shared passwords. We see shared passwords as an item that gets forgotten: local administrator, switch enable password, Wi-Fi key. For remote working rules, see the article remote working security policy.

Confidentiality agreements and the disciplinary process

6.6 requires confidentiality agreements to reflect the organization’s information protection needs and to be reviewed regularly. The typical gap in the field: a single template prepared years ago is used for everyone, and supplier staff have never signed anything. A confidentiality agreement should contain at least a definition of the information protected, the duration of the obligation, return or destruction of information at the end of the agreement, what happens in case of breach and the right to audit. Legal must approve the text, and signature records must be kept accessibly.

Two principles stand out in the 6.4 disciplinary process: the process must have been defined and announced before the violation, and it must be graduated according to the seriousness of the violation. The auditor usually looks at whether the disciplinary regulations refer to information security violations and how the regulations were communicated to employees. The details of a real disciplinary case contain personal data; they don’t need to be shown to the auditor. Anonymous evidence that the process exists and has been operated is enough.

We covered which evidence of awareness training is accepted in audits in the article training and awareness evidence. For designing role-based training content, see our ISMS awareness and role-based training service.

Physical security perimeter and entry control

The physical theme describes a layered structure. 7.1 covers defining security perimeters, 7.2 physical entry control, 7.3 securing offices, rooms and facilities, 7.4 physical security monitoring, 7.5 protection against physical and environmental threats and 7.6 working in secure areas. 7.4 is a new control introduced with the 2022 version; it requires unauthorized physical access to be detected with monitoring systems (cameras, alarms, door sensors).

Let the order of checks be:

  1. Classify the areas: Public areas (lobby, meeting rooms), working areas, secure areas (server room, archive, R&D, prototype area).
  2. Set the entry method for each boundary: Reception and visitor registration, badge access, badge plus a second factor (PIN or biometric) in secure areas.
  3. Manage entry permissions: Badge permissions are granted on request and approval, like access rights in information systems, and reviewed periodically. Don’t forget that the badge system and AD keep separate lists; the two don’t match up on their own.
  4. Set up monitoring: Cameras and door-held-open alarms on secure area doors; the retention period for recordings and who can view them should be defined.
  5. Assess environmental threats: Fire, flooding, extreme temperature, earthquake. In Türkiye, earthquake risk should be explicitly assessed in decisions on server room placement and anchoring cabinets.

A picture you may come across: the server room door has badge access, but the air conditioner’s drain pipe runs right over the rack. Door control alone doesn’t provide protection. For the technical details of server room design, see the article server room cabinet and rack layout on our network site.

Clear desk, screen and equipment security

7.7 covers the clear desk and clear screen rule, 7.8 equipment siting and protection, 7.9 security of assets off-premises, 7.11 supporting utilities (power, air conditioning), 7.12 cabling security and 7.13 equipment maintenance.

  • 7.7: The rule must be written down and supported technically: the automatic screen lock time should be enforced by group policy, and measures such as pull printing on printers should be considered. Evidence: the policy, a screenshot of the policy configuration and records of periodic floor checks.
  • 7.8 and 7.11: Servers and network devices in a locked cabinet; UPS and air conditioning maintained; temperature and humidity monitored. If there’s no date for the UPS battery test, maintenance isn’t considered done.
  • 7.9: Disk encryption for laptops and mobile devices, a rule against leaving them in vehicles, loss reporting.
  • 7.12: Protecting cables against damage and interception, labeling cabinets and patch panels.
  • 7.13: Maintenance records; protecting or wiping data on devices that leave for maintenance.

Storage media and secure disposal

7.10 covers managing storage media (USB sticks, external disks, backup cartridges, paper) from acquisition to disposal, and 7.14 secure disposal or reuse of equipment. Design the two together; the riskiest moment is when a device leaves the organization: a faulty disk sent back under warranty, a leased printer being returned, an old computer being donated. The internal disk of leased printers is the medium most often overlooked in the field.

A practical disposal approach:

  • Media to be reused: Wiping with a secure erase method supported by the manufacturer (e.g. cryptographic erase for SSDs or the manufacturer’s sanitize command) and verification. NIST SP 800-88 “Guidelines for Media Sanitization” is a common reference for classifying media sanitization methods.
  • Media to be destroyed: Physical shredding or a destruction service; services can be procured with reference to DIN 66399, which defines particle size security levels for paper and electronic media.
  • Record: A destruction report by serial number or the destruction company’s certificate; the asset’s status in the inventory updated to “destroyed”.
  • Personal data: For media containing personal data, alignment with the processes and records under the “Regulation on the Deletion, Destruction or Anonymization of Personal Data”.

Differences by location type

The same control is applied differently in the office, on the production floor and at a remote location. Treating locations separately in the risk assessment makes visible the differences behind a single “implemented” in the SoA. A shared HMI terminal on the production floor and a laptop at head office aren’t the same risk.

Topic Office Production floor Remote location / home
Entry control Reception, badge access Shift-based access, contractor entry Not under the organization’s control
Main risk Visitors, clear desk Open terminals, OT cabinets Device loss, screen being seen
Screen security Automatic lock Shared-use accounts, kiosks Lock and privacy filter
Equipment protection Locked server room Dust, vibration, temperature Disk encryption, VPN
Typical evidence Access logs, visitor book Cabinet lock check, site walk MDM report, signed commitment

Requirements get stricter in areas holding prototypes or physical parts owned by customers; for automotive suppliers we cover this in the article TISAX prototype protection.

Control–evidence table

Check Implementation Evidence in the audit
6.1 Screening Role-based verification list Verification record in a sample personnel file
6.3 Training Induction and annual training Attendance list, test results
6.5 / 5.18 Leaving Shared leaver checklist, reminder of obligations Comparison of leaving dates with account closure dates
6.6 Confidentiality Employee and supplier templates Signed samples, template review record
7.2 Physical entry Badge permission process Secure area permission list and its review
7.4 Monitoring Cameras and door alarm Recording retention setting, alarm test
7.7 Clear desk Policy and screen lock setting Site check record, policy setting
7.14 Disposal Wiping and destruction procedure Destruction report with serial numbers

You should have the evidence for every row in the table in hand before the audit. The auditor shouldn’t have to go looking for it. For the interpretation of organizational controls, see the article Annex A organizational controls, and for the general framework of the control texts, the ISO/IEC 27001:2022 page. We work on designing people and physical controls together with the rest of the ISMS as part of our ISMS setup and implementation consulting.

Frequently asked questions

Can a criminal record certificate be requested before hiring?

This depends on the nature of the role and the applicable legislation. The legal basis and proportionality of every document to be requested should be assessed together with HR and legal, and the candidate informed under KVKK. ISO 27001 requires screening to be proportionate to the role’s risk; it doesn’t mandate a specific document.

In a company with no server room that uses the cloud entirely, can physical controls be excluded?

Some can be excluded; but controls such as office entry, clear desk and screen, security of devices off-premises and secure disposal remain applicable in most cases. Physical security on the data center side is addressed through supplier controls, using the cloud provider’s assurance reports.

How quickly should a leaver’s account be closed?

The standard doesn’t give a time; the organization sets the time itself based on its risk assessment and writes it into the procedure. The auditor tests whether this time is met by comparing leaving dates with account closure records.

Is the destruction company’s certificate enough for disk destruction?

If the certificate includes serial numbers and matches the records in the inventory, it’s strong evidence. Bulk reports without serial numbers don’t show which media were destroyed; they remain weak.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles