How do we…
How do we decide which pre-employment screening and employment terms our ISMS needs?
Add to board memoOpen the memo
The short answer
- Recommendation
- Set proportionate checks by role, confirm with HR and your legal adviser what each country allows, extend the checks to contractors through the contract, and block access until the check is complete. Sample recent joiners to prove it.
- Reasoning
- Auditors sample recent joiners, contractors included, and look for checks done for some roles and not others with no reason recorded, and for checks completed after access started. The law on what you may check differs by country, so a single checklist copied from elsewhere can itself be a breach.
- Considerations
- The standard's text is paywalled. The controls are described from the pack's Library and public guides, which are secondary.
- Screening and the data it creates are regulated by employment and data protection law that varies by country. CISO Times states no country rules.
- Smaller organisations can describe their approach in the Statement of Applicability. Larger ones usually write a screening procedure.
- The control asks for checks before people join and on an ongoing basis, within the law. Set a rule with HR and your legal adviser for when existing staff are checked again, for example on a move into a more sensitive role.
The decision, step by step
Select any step for the reasoning behind it and where the pack covers it.
- Start
- Step
- Decision
- Outcome
- Loop back
Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.
Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one. A code beside a source, such as RR-17, is the number of a rule in that pack document; the document lists its rules.
Read as text
The same flow written out: each step, its reasoning and where the pack covers it. 21 steps.
Start
People join us and we need screening and terms the ISMS can stand on
Three Annex A controls meet here: screening of people before they get access, terms of employment that carry security duties, and confidentiality agreements. The auditor samples recent joiners, contractors included. The decisions are how deep the checks go for each kind of role, what the law lets you check, and who proves it was done before the first day of access.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Group roles by what they can reach
List the kinds of role and what each can see or do: customer data, privileged access, money, source code. Three or four groups are enough. This is the basis for proportionate checks, and it uses the same classification and access thinking as the rest of the ISMS.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
- P15-A03 Classification Level Handling Rules MatrixHandling matrix
Step
Set the checks for each group
The pack's guidance is proportionate checks by role: identity and, where the law requires or allows, right to work for all, references and qualifications for most, deeper checks for privileged or finance roles. Write the levels down as a standard. A standard that applies the same check to everyone, or to no one, is hard to defend. Say when existing staff are checked again.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Does the law where each person works allow each check?
What you may ask about, check and keep differs by country and sometimes by role, and data protection and employment law both bite. CISO Times gives no country rules. Not known takes the no branch, because a check that breaks the law is worse than none.
- Yes: Do contractors and agency staff with access get equivalent checks?
- No, or not known: Ask HR and legal for each country, then adjust the standard
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Ask HR and legal for each country, then adjust the standard
Ask them which checks are allowed, what consent or notice is needed, how long results can be kept and who may see them. Drop or change a check that is not allowed and say so in the standard. Do not copy another country's practice.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Do contractors and agency staff with access get equivalent checks?
The control covers people who are not on your payroll too. A common finding is contractors engaged on the agency's paperwork alone. Either the agency or supplier does the checks and shows evidence, or you do them.
- Yes: Is every check complete before access starts?
- No, or not known: Put the check in the agency or supplier contract; ask for evidence
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
- P13-A03 Joiner-Mover-Leaver Operating ProcedureJoiner (non-employee)
Step
Put the check in the agency or supplier contract; ask for evidence
Say which checks are required for which kind of access, who does them, and that you may ask for confirmation. Keep the confirmation with the access request. If neither the agency nor the supplier will do them, do them yourselves or limit the access.
In the pack
- P06-A07 Supplier Contract Security Clause LibraryClause selection matrix
Decision
Is every check complete before access starts?
The common mistake in the pack's guidance is checks done after access is already granted. A rule on paper does not prevent that. Make completion a condition of the access request, so the account cannot be created without it.
- Yes: Do contracts state security duties, including after leaving?
- No, or not known: Make completion of the check a condition of the access request
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
- P13-A03 Joiner-Mover-Leaver Operating ProcedureJoiner (employee)
Step
Make completion of the check a condition of the access request
Have HR or the agency confirm completion before the account is created. For an urgent start, agree a narrow route in advance: limited access until completion, approved by a named person and recorded. Treat it as an exception, not as the way things are done.
In the pack
- P13-A03 Joiner-Mover-Leaver Operating ProcedureJoiner (employee)
Decision
Do contracts state security duties, including after leaving?
Employment contracts and contractor agreements should carry confidentiality and security responsibilities and refer to the policies. A common finding is old templates without security terms still in use. Sign before access, not after.
- Yes: Do outsiders sign a confidentiality agreement before they see secrets?
- No, or not known: Add the security terms to the templates with Legal
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Add the security terms to the templates with Legal
Include confidentiality, responsibility for following the security policies, and obligations that continue after the person leaves. Make sure the terms are signed before access. Fix current staff on old templates at the next change, as the law allows, and not only new joiners.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Do outsiders sign a confidentiality agreement before they see secrets?
Third parties include customers, partners, consultants and suppliers before a full contract is signed. The usual mistake is information shared before the agreement exists, or agreements with no end date or return clause.
- Yes: Have people acknowledge the security policies and keep the record
- No, or not known: Keep standard agreements and record who has signed
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Keep standard agreements and record who has signed
Keep templates reviewed by Legal, with an end date and a return or destruction clause. Record who has signed and review the templates when needs change. The rule is simple: no confidential information goes out before the signature.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Have people acknowledge the security policies and keep the record
The terms refer to the policies, so people must have seen them. Keep the acknowledgement with the personnel record, and use the induction material to explain what is expected.
In the pack
- P16-A06 New Joiner Security Induction Deck
- P04-A07 Policy Attestation & Acknowledgement TrackerInstructions
Step
Write the rule for adverse results before the first case
Decide who judges whether a result matters for the role, what the person can say in reply, and who decides. Local law may limit what you can take into account. The hiring decision stays with HR and the hiring manager. Security advises on the access risk. Write the rule now, even if no case has come up.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Decision
Does a check give an adverse or unclear result?
A result has come back that is adverse or unclear for the role. The rule you wrote decides what happens next. If no case has come up yet, the rule is still written and waiting.
- Yes, or not known: Follow the rule: judge relevance, hear the person, record the decision
- No: Sample recent joiners, contractors included
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Follow the rule: judge relevance, hear the person, record the decision
Judge the result against the role and its access, give the person a chance to explain where the law and fairness require it, and record who decided and why. Do not hold results longer than the law allows. Offer a lower-risk role or access where that is sensible.
In the pack
- P08-A03 Annex A Control Implementation LibraryControl Library
Step
Sample recent joiners, contractors included
Take a sample of recent joiners and contractors and check each against the standard: the checks complete before access, the terms signed, the policies acknowledged. Include people who started in a hurry. This is what the auditor samples, and the usual finding is checks done for some roles and not others with no reason recorded.
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideCommonly sampled Annex A controls
Decision
Did the sample show someone without a completed check or signed terms?
Any gap is a finding about the process, not only about the person. Fix both: complete the check or remove the access, then fix the step that let it through.
- Yes: Complete the check or remove access, fix the gate and sample again
- No: Screening and terms set by role, applied before access and sampled
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideCommonly sampled Annex A controls
Step
Complete the check or remove access, fix the gate and sample again
Complete the missing check, or remove the access until it is done. Find why the gate failed and close it, whether it was a hurry, a missing HR step or an agency that did not confirm. Then take a fresh sample.
- Then: Sample recent joiners, contractors included (back to an earlier step)
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideCommonly sampled Annex A controls
Outcome
Screening and terms set by role, applied before access and sampled
Keep the standard, the legal advice on what you may check, the sample result and the signed terms. Do not say all staff are vetted if some roles are not checked, or that checks are the same in every country. Say what you do and where the law limits it.
In the pack
- P08-A10 Stage 1 and Stage 2 Audit Preparation GuideCommonly sampled Annex A controls
Practical checklist
- Group roles by what they can reach.
- Set the checks for each group, write the standard and say when existing staff are checked again.
- Confirm with HR and your legal adviser what each country allows.
- Cover contractors and agency staff through the contract and ask for evidence.
- Make completion a condition of the access request.
- Check contracts, confidentiality agreements and acknowledgements, then sample recent joiners.
Evidence to have ready
- The screening standard by role, with the legal advice behind it.
- Completion records for a sample of recent joiners and contractors.
- Contract templates with the security terms and signed copies.
- Signed confidentiality agreements and policy acknowledgements.
Assumptions
- Roles have named owners, and HR can confirm when a check is complete.
- A legal adviser can say what each check allows in each country where you employ or engage people.
- You can stop an account being created until HR or the agency confirms completion.
Not covered here
- Setting up a new starter's access before the first day. That is “How do we set up a new starter's access before their first day?”.
- Removing a leaver's access. That is “When must a leaver's access be removed, and what changes if they leave on bad terms?”.
- Showing that staff are aware and that those running the ISMS are competent. That is “How do we show that the people running our ISMS are competent and that our staff are aware?”.
- The response to a policy breach by staff. That is “If a member of staff breaks the security policy, then how do we decide the disciplinary response?”.
Related questions
- How do we set up a new starter's access before their first day?
- When must a leaver's access be removed, and what changes if they leave on bad terms?
- How do we show that the people running our ISMS are competent and that our staff are aware?
- How do we get staff to acknowledge policies, and chase those who don't?
- If a member of staff breaks the security policy, then how do we decide the disciplinary response?