A learned profile of how people, vendors, and systems normally interact inside an organisation. It includes tone, timing, recipients, and request structure, giving security teams a reference point for spotting messages that are socially engineered but technically clean.
What a communication baseline captures
A communication baseline is not a rulebook, it is a learned pattern of normal interaction. It captures who usually talks to whom, how requests are framed, when messages arrive, and what language is typical, so defenders can compare routine behaviour with suspicious but technically valid messages.
That makes the baseline useful in environments where social engineering succeeds without malware, because the message may look legitimate to security tooling while still being unusual for the organisation’s own communication culture. The value is the comparison point, not the message content alone.
Why it matters for human and vendor interactions
Baselines are especially useful where trust is distributed across employees, suppliers, finance teams, support staff, and automated business processes. Many attacks exploit the normality of routine workflows, then insert a request that is slightly off in timing, tone, recipient chain, or approval path.
Security teams use the baseline to spot those small deviations before they become losses. A request that arrives from the right general channel but breaks the expected sequence can be more suspicious than a message with obvious errors, because attackers often study the organisation first and then imitate its cadence.
For defensive maturity, the baseline should reflect how the business actually operates, not how a policy says it should operate. If the baseline is built from idealised behaviour, it will miss the practical patterns that matter most during review.
How analysts use it for detection and triage
Communication baselines work best as an investigation aid, not as an automated verdict. Analysts compare the message against normal sender-recipient relationships, timing patterns, escalation habits, and the structure of the ask, then decide whether the deviation is benign, accidental, or potentially engineered.
A useful baseline also helps reduce false positives. Teams can distinguish a genuine business exception, such as a one-off urgent request, from a forged or hijacked account that is using familiar names but an unfamiliar interaction pattern.
Because the subject is behaviour, not just content, the strongest detections often combine mailbox, collaboration, ticketing, and workflow context. That broader view makes it harder for an attacker to stay “technically clean” while still behaving unlike the organisation’s normal communications.
What it does and does not prove
A communication baseline is a reference model, not proof of compromise. Unusual timing or tone can indicate risk, but it does not by itself show malicious intent, and a skilled attacker may still stay inside the normal pattern well enough to pass a superficial check.
The baseline is most useful when paired with identity verification, process validation, and independent callback or approval checks for sensitive requests. It should sharpen judgement, not replace it.
Teams also need to refresh the baseline as the business changes. Mergers, new vendors, organisational restructuring, and remote-work patterns can all shift normal behaviour, so a stale baseline can become misleading very quickly.
Risk and Threat Considerations
Communication baselines matter because social engineering often succeeds by appearing ordinary. Attackers exploit familiar tone, expected timing, and trusted relationships to bypass suspicion, especially when the request is internally plausible and does not trigger technical controls.
Failure mechanism: A forged or hijacked message can imitate routine communication closely enough that staff treat it as business as usual, allowing fraudulent requests, data exposure, or process abuse to proceed.
Impact: The result can be payment diversion, credential theft, unauthorized disclosure, or approval-chain compromise, often before traditional security monitoring sees anything abnormal.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-14 — Security Awareness and Skills Training | Communication baselines support training users to notice social engineering patterns. |
| Recommendation — Train users to compare suspicious requests against normal interaction patterns before acting. | ||
| NIST CSF 2.0 | DE.AE-02 — Anomalous Events are Detected | Baselines define what normal communication looks like so deviations can be detected. |
| PR.AT-01 — Users are Provided Awareness and Training | Baseline-driven review depends on people recognising social engineering cues in ordinary workflows. | |
| Recommendation — Compare observed communication patterns against baseline behaviour to surface anomalies. Provide awareness training that teaches staff to question unusual requests even when messages appear legitimate. | ||
| NIST SP 800-53 Rev 5 | AU-6 — Audit Record Review, Analysis, and Reporting | Communication baselines rely on reviewing message and workflow patterns for suspicious deviations. |
| SI-4 — System Monitoring | Baseline comparison is a monitoring technique for detecting suspicious but technically valid behaviour. | |
| Recommendation — Review communication and workflow records for deviations from normal request patterns. Monitor communication activity for anomalies in timing, recipients, and request structure. | ||
Practitioner Guidance
What to watch for: Treat the baseline as a living reference, not a static policy artifact. The most useful signals are small structural deviations, such as an unusual recipient sequence, a sudden change in urgency, or a request that skips the normal approval path while still sounding professionally credible.
Practitioner takeaway: The best communication baseline programs combine behavioural context with process checks, because the goal is to spot messages that fit the language of the business but not its normal operating rhythm.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org