By NHI Mgmt Group Editorial TeamBased on Knowbe4: “A Strategic Framework for Human Risk Management: What is HRM and Why Do Organizations Need It?” (January 9, 2026)

TL;DR: Human factors contribute to 68% to 90% of security breaches, and KnowBe4’s whitepaper argues that Human Risk Management shifts organisations from awareness campaigns to continuous identification, measurement, and mitigation of people-related risk. The strategic question is no longer whether users make mistakes, but whether security programmes can operationalise human-risk controls fast enough to keep pace with AI-amplified social engineering.


At a glance

What this is: This whitepaper frames human risk management as a shift from awareness campaigns to continuous identification, measurement, and mitigation of people-related security risk.

Why it matters: It matters because security teams need governance that reduces human-derived exposure at programme level, especially as AI makes social engineering more scalable and harder to spot.

By the numbers:

  • The human element remains a factor in 68% to 90% of security breaches.

Context

Human risk management is a governance response to a familiar security problem: people are still part of the attack surface, but awareness alone does not reliably change behaviour or stop delivery of modern phishing and impersonation campaigns. In practice, teams need a way to measure exposure, not just deliver training, because the control gap is no longer only technical.

The article ties that gap to AI-amplified social engineering, which lowers attacker effort and raises the quality of lures. That matters for IAM, PAM, and NHI programmes because human error, credential misuse, and trust failures often become the first step in credential theft, privilege abuse, or delegated access compromise.


Key questions

Q: What breaks when human risk management is only treated as training?

A: Training alone breaks because it changes knowledge, not exposure. Users can still click, approve, share, or misuse access if identity controls and privilege boundaries remain unchanged. Human risk management works best when behaviour data is combined with IAM and PAM context so interventions target the users and roles that can actually cause material damage.

Q: Why does AI-assisted social engineering increase risk for identity security programs?

A: AI-assisted social engineering increases risk because it lowers the cost of tailored manipulation while making messages and conversations look more authentic. That shifts attacks from obvious spam to credible interaction at scale. Once attackers can personalize context and sustain dialogue, users are more likely to trust the request, click a link, or reveal credentials.

Q: How can organisations tell if human-risk management is working?

A: Look for downward trends in behavioural susceptibility, improved performance in realistic simulations, and better targeting of coaching to higher-risk groups. If the programme only reports attendance or click rates, it is measuring activity, not security improvement.

Q: How should teams connect red team results to IAM and PAM governance?

A: Any exploit path that uses leaked credentials, overprivileged access, or lateral movement should be routed to IAM and PAM owners as a control issue, not just an application defect. That ensures identity, privilege, and access scope are remediated alongside code and network fixes.


Technical breakdown

Why awareness programmes fail under AI-amplified social engineering

Awareness programmes assume users can reliably recognise hostile prompts in time to act differently. That assumption weakens when attacks are personalised, context-rich, and delivered at scale by AI-assisted tooling. Human risk management treats the user population as a measurable control surface, not a training completion metric. The mechanism is continuous measurement, segmentation, and intervention based on observed behaviour, role, and exposure rather than one-time education alone.

Practical implication: replace generic awareness cadence with behaviour-based risk measurement and targeted intervention by role and exposure.

How human risk becomes an access problem

Human error becomes an identity problem when a trusted person clicks, approves, or discloses something that changes access conditions. In many incidents, the human element is the path into credentials, sessions, or delegated workflows, which then becomes the real security event. That is why HRM belongs alongside IAM and PAM governance, especially where approval fatigue, weak verification, or poor reporting channels allow social engineering to convert attention failures into access failures.

Practical implication: align human-risk controls with identity and privileged-access workflows so mistakes do not become standing access paths.

What a data-driven HRM model actually governs

A data-driven HRM model does not just count training completions. It measures susceptibility, reporting speed, role-based exposure, and the effectiveness of interventions over time. The goal is to turn people-related risk into something the security programme can prioritise, monitor, and reduce, much like other control domains. That makes HRM a governance layer for behavioural risk, not a replacement for technical controls.

Practical implication: define human-risk metrics that can be reviewed alongside other security controls and tied to remediation ownership.


Threat narrative

Attacker objective: The attacker’s objective is to convert a human mistake into access that bypasses stronger technical controls.

  1. Entry begins with AI-amplified social engineering that makes phishing, impersonation, and other human-targeted lures more convincing and more deliverable at scale.
  2. Credential access or workflow abuse follows when a user discloses information, approves an action, or interacts with a malicious prompt that changes trust conditions.
  3. Escalation occurs when the attacker turns that human mistake into access to accounts, sessions, or delegated processes that were never meant to be exposed.
  4. Impact is achieved through breach progression that starts with people and ends with compromised systems, data, or privileged operations.
  • Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
  • CISA Private-CISA GitHub leak 2026: A CISA contractor's public GitHub repo exposed AWS GovCloud admin keys, Artifactory credentials and plaintext passwords for six months.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.


NHI Mgmt Group analysis

Human risk has become a governance problem, not a training problem. The article is right to move the discussion away from blame and toward control design. Security teams still over-rely on awareness completion as a proxy for resilience, even though modern attacks succeed by exploiting time pressure, context, and trust. Practitioner conclusion: treat human-risk reduction as an operating model with metrics, ownership, and continuous review.

AI has widened the delivery advantage for attackers before defenders have improved the measurement model. When social engineering becomes more personalised and scalable, the old assumption that users can spot suspicious behaviour breaks down faster than traditional awareness programmes can adapt. This is also where identity governance enters the picture, because many human-risk events end in credential use, approval abuse, or delegated access. Practitioner conclusion: tie human-risk governance to identity and privileged-access controls, not to training alone.

Human Risk Management is best understood as a control plane for behavioural exposure. The key shift is from counting sessions delivered to measuring susceptibility, reporting behaviour, and remediation effectiveness. That creates a named concept worth using across programmes: human-risk control plane, the layer that turns people-related exposure into something the security function can monitor and reduce. Practitioner conclusion: build human-risk metrics into the same governance rhythm used for other security controls.

The article validates a broader security reality: the breach chain often starts in human trust and ends in technical compromise. That makes human-risk work relevant to IAM, PAM, and NHI governance because attackers rarely need to defeat every control if one person can be manipulated into opening the door. Practitioner conclusion: design verification, reporting, and escalation paths so that human trust cannot be used as an uncontrolled access pathway.

From our research library:

  • 74% of all breaches included the human element, through error, privilege misuse, stolen credentials or social engineering, according to Verizon's 2023 Data Breach Investigations Report.

What this signals

Human-risk control plane: organisations need a control layer that turns behavioural exposure into something measurable, reviewable, and actionable. Without that layer, human-risk work stays stuck in awareness metrics that do not tell security leaders whether trust is actually getting safer.

Security teams should expect human-risk governance to sit closer to identity controls over time, because the most damaging user mistakes often become credential, session, or approval events rather than isolated awareness failures.


For practitioners

  • Define human-risk metrics that matter Track susceptibility, reporting speed, repeat exposure, and intervention effectiveness instead of relying on training completion alone.
  • Bind HRM to IAM and PAM workflows Use identity and privileged-access controls to limit what a mistaken approval, disclosure, or click can unlock.
  • Segment interventions by role and exposure Prioritise high-risk roles, frequent approvers, and users with elevated access when tailoring simulations, coaching, and controls.
  • Measure whether users can report suspicious activity quickly Treat reporting behaviour as an operational control signal, because fast escalation often matters more than perfect detection by the individual recipient.

Key takeaways

  • Human error remains a material breach driver, but the governance failure is treating that exposure as a one-off awareness issue instead of an ongoing control problem.
  • AI-amplified social engineering raises the likelihood that users will be manipulated faster than traditional detection and training cycles can adapt.
  • The strongest response is to measure human susceptibility, tie it to identity controls, and manage it as part of continuous security governance.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AT-01 — Awareness and TrainingThe article challenges awareness-only programmes as insufficient against human-targeted attacks.
GV.OV-01 — Oversight of the cybersecurity strategyHRM is framed as a governance layer for people-related risk, not a standalone training activity.
Recommendation — Use PR.AT to measure whether awareness changes behaviour, not just completion rates. Place human-risk metrics under executive oversight and review them as part of security governance.
NIST SP 800-53 Rev 5AT-2 — Awareness TrainingTraining is part of the article, but the piece argues it must be paired with measurable risk reduction.
Recommendation — Treat AT-2 as one control in a wider human-risk programme and validate its effect with behaviour data.
MITRE ATT&CKTA0001;TA0006 — Initial Access; Credential AccessAI-assisted social engineering is the entry path that often leads to credential compromise.
Recommendation — Map human-targeted lure activity to TA0001 and TA0006 to prioritise phishing-resistant controls and response.

Key terms

  • Human Risk Management: The practice of managing how people interact with security controls, especially under pressure, distraction, or deception. It combines training, policy, and friction management so identity systems are still usable enough that users do not bypass them in day-to-day work.
  • AI-amplified social engineering: AI-amplified social engineering is the use of generative or automated systems to make deception more convincing, scalable, and personalised. It increases the volume and realism of lures, which raises the pressure on users and weakens traditional awareness-only defences.
  • Behavior-Based Risk Model: A behavior-based risk model evaluates user activity patterns to determine whether action looks normal, suspicious, or high risk. It combines signals such as access timing, data movement, and interaction context. In practice, it helps analysts distinguish routine work from behaviour that may need intervention or review.
  • Human-Risk Control Plane: A human-risk control plane is the governance layer that turns behavioural exposure into measurable security data and intervention decisions. It connects awareness, reporting, identity controls, and remediation into one repeatable programme instead of leaving people risk scattered across isolated awareness efforts.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance and secrets management alongside the identity controls that shape operational risk. It is designed for practitioners who need to connect identity security decisions to broader programme governance.
NHIMG Editorial Note
Published by the NHIMG editorial team on August 2, 2026.
Updated on October 12, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org