A runtime security method that combines identity, data, model behaviour, agent posture, and environment signals into one assessment. It is designed to answer whether agent activity was appropriate in context, not merely whether a request was authorised.
Expanded Definition
Five-signal correlation is a runtime evaluation pattern for NIST Cybersecurity Framework 2.0-style decisioning in which identity, data, model behaviour, agent posture, and environment are assessed together. In NHI operations, it helps determine whether an AI Agent’s action is not only authenticated, but also contextually appropriate.
The key distinction is that this is not a single control or a fixed score. It is a correlation method that can sit above RBAC, PAM, and ZTA policy layers, combining signals that often live in separate systems. For example, an agent may be authorised to call a tool, but the request may still be abnormal if the model is producing risky output, the Secrets are stale, or the runtime environment has drifted from expected posture. Guidance across vendors varies, and no single standard governs this yet, so implementations differ in which five signals are chosen and how they are weighted.
The most common misapplication is treating five-signal correlation as a post hoc audit report, which occurs when organisations only evaluate the signals after the action has already executed.
Examples and Use Cases
Implementing five-signal correlation rigorously often introduces latency and integration overhead, requiring organisations to weigh stronger contextual enforcement against slower agent execution and more complex policy tuning.
- An agent requests database access, and the platform checks its NHI identity, the sensitivity of the target data, the model’s recent tool-use pattern, the agent’s signed posture, and the host environment before allowing the call.
- A code-generation workflow is allowed to write to a repository only when the model output is low risk, the agent is running from a trusted workload, and the request matches the expected environment and data scope.
- A secrets rotation job is denied because the agent identity is valid, but the runtime context shows an unusual destination, which changes the overall assessment even though the request was technically authorised.
- A privileged assistant is allowed to proceed after a Ultimate Guide to NHIs-style governance review confirms that the identity is managed, the posture is healthy, and the environment matches the approved deployment baseline.
Practitioners often compare this pattern to broader identity and AI controls in NIST Cybersecurity Framework 2.0 and NIST-style zero trust thinking, even though the exact signal set is still evolving. The practical goal is to reduce blind trust in any single indicator.
Why It Matters in NHI Security
Five-signal correlation matters because NHI compromise rarely appears as a simple login failure. Attackers often exploit valid identities, trusted automation, and weak runtime oversight at the same time. NHI Management Group research shows that 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, which underscores why isolated checks are not enough. The same operational logic applies to agentic systems, where a valid credential does not prove that an action was safe in context. The Ultimate Guide to NHIs also shows that 97% of NHIs carry excessive privileges, making contextual enforcement especially important when agents can reach sensitive tools or data.
This concept also aligns with the broader direction of NIST Cybersecurity Framework 2.0, which emphasizes governance, access control, and continuous risk awareness rather than one-time approval. For NHI teams, five-signal correlation becomes most valuable when privilege boundaries are unclear, model behavior is changing, or environmental trust has weakened.
Organisations typically encounter the need for five-signal correlation only after an agent misuse incident, at which point the term becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-05 | Contextual runtime checks reduce abuse of overprivileged non-human identities. |
| OWASP Agentic AI Top 10 | A-03 | Agentic controls emphasize monitoring tool use, behavior, and execution context. |
| NIST Zero Trust (SP 800-207) | SA-3 | Zero trust requires continuous, context-aware authorization decisions. |
Reassess trust continuously using identity, device, workload, and environment signals.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on June 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org