Standard: The company manages personnel-related integrity, security and continuity risks throughout the employment lifecycle. Recruitment, , role changes and offboarding are proportionate to the role and support the protection of , critical operations and partner commitments without creating unnecessary barriers to hiring.
DefTech companies may hire quickly because of growth, urgent production needs, technical shortages, battlefield demand or new partner commitments
Recruitment may rely on trusted networks, referrals, former colleagues, volunteers, contractors, advisors or military-linked contacts
People may start contributing before all formal HR steps are completed
S Security
Personnel may access sensitive technical data, source code, prototypes, production information, routes, locations, customer or end-user information, military-linked information or restricted project materials
R Regulatory
Employment law, data protection, anti-corruption, sanctions, export-control, confidentiality and contractual obligations may affect the design of recruitment, screening, , role changes and offboarding processes.
The information companies may obtain, retain or use when conducting personnel screening or ongoing integrity monitoring may be limited by legal, contractual or data protection requirements.
C Cultural
Small and founder-led teams may rely on trust and personal recommendation rather than formal checks
People may hold multiple roles, move quickly between functions or work informally across teams
Sensitive concerns may be difficult to raise where relationships are close or the person is technically critical
RES Resource
Companies may not have a large HR function or dedicated compliance/security screening capacity
Topics
6 topics, each written at three levels. Each level assumes the one before it.
13.1
Role risk classification before engagement
Getting started
Identify whether the role is standard, sensitive or critical before engagement. Examples may include access to funds, procurement, contracting, , technical data, critical systems, export-related activities, public-sector interactions or key customer and partner relationships.
Keep the classification simple
Developing
Define role risk categories and link them to proportionate screening, , access controls and approval requirements.
Establish criteria for identifying sensitive and critical roles, taking into account the level of authority, access, decision-making and business impact. Examples may include finance, procurement, contracting, security, HR, export interface, business development, partner management, technical leadership and system administration
Reassess the role if responsibilities change
Advancing
Maintain and periodically review a role risk map covering sensitive and critical positions across the organisation.
Link each role category to screening level, onboarding content, access rules, conflict-of-interest expectations, authority limits and offboarding requirements
Review the map when the company grows, restructures, enters new partnerships, starts export activity or adds sensitive projects
13.2
Integrity-informed recruitment decisions
Getting started
Consider basic integrity and security information where the role has been classified as sensitive or critical
Where concerns are identified, consider whether they affect the person's role, level of access, supervision or suitability for the position.
Developing
Take integrity and security information into account when deciding whether to hire, engage or assign a person to a sensitive role
Record material concerns and the decision made, including any safeguards, restrictions or additional approvals
Make sure similar concerns are treated consistently
Advancing
Adjust role scope, access, supervision, conflict-of-interest measures or approval authority where proportionate.
Be able to explain how identified concerns influenced the engagement decision and any safeguards applied.
13.3
Pre-engagement checks and screening level
Getting started
Define minimum checks before engagement for standard roles. Examples may include identity confirmation, right to work where relevant, employment or experience verification, and references where feasible.
For sensitive and critical roles, determine whether additional checks are required before granting access to the role.
For sensitive and critical roles, do not rely solely on personal trust, referrals or technical competence instead of proportionate pre-engagement checks.
Developing
Match screening level to role risk
For sensitive and critical roles, consider additional checks such as reference checks, conflict-of-interest disclosure, sanctions or restricted-party screening where relevant, adverse media review, qualification verification or previous responsibilities involving or critical systems, where relevant.
Record what was checked and any gaps
Advancing
Maintain a practical screening matrix linked to role risk and review it periodically.
Define standard and enhanced checks for different role types, including employees, contractors, advisors and temporary personnel
Use time-limited or where urgent engagement is needed before all checks are complete
13.4
Role-based onboarding and integrity expectations
Getting started
New personnel receive practical covering the company's expected behaviours, confidentiality, conflicts of interest, reporting concerns and appropriate handling of company information.
Onboarding may be simple and practical, but it should happen before or soon after the person starts work
Access to , systems or responsibilities should not be granted before minimum onboarding is completed.
Developing
Adapt onboarding to the person’s role and access
Personnel in sensitive or critical roles receive additional guidance relevant to their responsibilities and level of access. This may include decision authority, , conflicts of interest, handling of sensitive information, third-party interactions, donations and sponsorship, arrangements, access rules or other role-specific expectations.
Advancing
Maintain structured role-based onboarding for sensitive and critical roles.
Include practical scenarios and expected behaviours linked to the role
Update onboarding when roles, risks or company activities change
13.5
Safeguards for sensitive and critical roles
Getting started
Nothing additional at this level.
Developing
Apply additional safeguards proportionate to the role. Examples may include conflict-of-interest disclosure, additional approval, limited access, supervision, access review, segregation of duties, enhanced or periodic check-in
Define which safeguards apply to different categories of sensitive roles.
Advancing
Maintain a list or map of sensitive and critical roles and the safeguards applied to them
Review sensitive and critical roles when responsibilities, authority, access, systems, projects or activities change
Use incidents, integrity concerns, access reviews, investigations, partner findings or other relevant experience to improve safeguards for sensitive roles.
13.6
Personnel integrity concerns and escalation
Getting started
Identify when personnel behaviour may create integrity, security, financial, operational or partner trust concerns
Recognise behaviours that may create integrity, security, operational or partner trust concerns, such as attempts to bypass controls, misuse of company resources, confidentiality breaches, conflicts of interest or other inappropriate conduct.
Escalate material concerns rather than handling everything informally
Developing
Define responsibilities for managing different types of personnel conduct concerns, including when HR, management, legal/compliance, security or external support should be involved.
Record material concerns, actions taken and any restrictions or safeguards
Protect confidentiality and avoid against people who raise concerns
Advancing
Maintain a consistent process for managing material or repeated personnel conduct concerns.
Link conduct issues to , conflict-of-interest management, access rights, sensitive-role safeguards, disciplinary action and corrective measures
Use repeated issues to improve , manager expectations, controls and role design
You have found the engineer you urgently need for a critical project and they can start tomorrow. But the role gives access to sensitive technology and systems, and completing all checks before granting access could delay work the team cannot afford to postpone.