What evidence do auditors commonly ask for on HR-02 Employment terms and conditions?

Employment and contractor agreement templates showing the information security obligation clause; Signed or electronically captured policy acknowledgements for a sample of personnel; Comparison report of acknowledgement timestamps against account provisioning timestamps; Onboarding checklist that makes acknowledgement a precondition for account creation.

What is the most common gap auditors find on HR-02?

Accounts opened first and the acknowledgement chased up afterwards

BSI C5 (121-criteria catalogue) · C5: Human Resources

`HR-02` Employment terms and conditions

Bind internal and external personnel through their employment or engagement terms to the applicable security policies, and capture a documented acknowledgement of the security policy and its subordinate instructions before any access to customer data or production components is granted.

Source: BSI C5 (121-criteria catalogue), HR-02. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open BSI C5 (121-criteria catalogue) in the compliance library.

The edition of the catalogue is not stamped here; check the edition your attestation is issued against.

artefacts

held by a system

at each review

hard

to go live

Vendor register / contract repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

Signed or electronically captured policy acknowledgements for a sample of personnel · HR system / LMS
Comparison report of acknowledgement timestamps against account provisioning timestamps · Identity provider / directory

governing documentDocuments that govern the control

Employment and contractor agreement templates showing the information security obligation clause · Vendor register / contract repository
Onboarding checklist that makes acknowledgement a precondition for account creation · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Accounts opened first and the acknowledgement chased up afterwards
Acknowledgement recorded against a policy version that has since been superseded
Agency and freelance personnel sign no equivalent undertaking
Acknowledgement taken once at hire and never renewed after major policy revisions

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

HR-01 Verification of qualification and trustworthiness · HR-03 Security training and awareness programme