Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Relationship Context
Cyber Security

Relationship Context

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Relationship context is the surrounding knowledge that helps a person judge whether a request is normal, expected, and properly authorised. In email security, it includes who usually communicates with whom, how often they interact, and whether the timing and format match past behaviour. Without it, routine-looking fraud becomes much harder to spot.

How relationship context works

Relationship context is the background knowledge that makes a request feel normal, expected, and authorised. In practice, it is the pattern behind the message, who usually talks to whom, how those interactions typically begin, and whether the tone, timing, and format fit the established relationship. That context turns a raw message into something people can judge.

In security terms, relationship context is a trust signal, not proof. It helps distinguish a routine request from a spoofed one, but it should never be treated as a standalone authorisation mechanism. When the context is weak, stale, or missing, attackers can imitate familiar communication patterns and look legitimate enough to bypass casual review.

Why it matters in email security

Email is one of the clearest places where relationship context matters because attackers often exploit familiarity rather than technical flaws. A request that appears to come from a known supplier, colleague, executive, or support contact can seem credible if it matches a usual communication pattern. The danger is strongest when the message is plausible on its face and only slightly out of character.

Strong relationship context raises the cost of deception by giving reviewers a baseline for comparison. Weak context, by contrast, makes it harder to notice subtle fraud such as unusual urgency, changed bank details, unexpected attachments, or a shift in reply style. That is why relationship context is often one of the first things lost in impersonation and business email compromise attempts.

In modern environments, that baseline is not static. Teams change, vendors rotate contacts, and new workflows emerge, so the surrounding context must be refreshed rather than assumed. If an organisation no longer knows what “normal” looks like for a relationship, the control weakens even if the mail system itself is functioning correctly.

What changes when the context is missing

Without relationship context, defenders lose a practical way to separate ordinary business communication from suspicious activity. A message can still be technically valid, properly formatted, and sent from a trusted domain, yet remain deceptive because the surrounding relationship does not fit the story it tells. That is why authentication alone does not solve social engineering.

Missing context also reduces detection quality. Security teams may see a single message as harmless, while a human reviewer might recognise that the sender never uses that tone, never sends requests at that hour, or never starts a conversation in that way. Relationship context adds the behavioural layer that makes those discrepancies visible.

For organisations, the consequence is not just mistaken trust. Once a fraudulent request is accepted, the next step is often payment diversion, credential capture, session theft, or approval of a malicious change. The initial weakness is not in transport or syntax, but in the judgement that the request belongs in the existing relationship.

How practitioners should use it

Practitioners should treat relationship context as part of the decision process, not as a feeling. The useful question is whether the request fits the established pattern well enough to be accepted, and if not, what additional verification is needed before action is taken.

MITRE ATT&CK Enterprise Matrix is useful here because it helps teams think about credential access, impersonation, and the attack chain that follows a successful deceptive message. Relationship context is often the human-side clue that interrupts that chain before a malicious request turns into compromise.

OWASP API Security Top 10 is a reminder that trust decisions must be enforced by explicit controls when a request can trigger business action. When a request looks normal but should not be trusted, the organisation needs a stronger control than familiarity alone.

Practitioner note: the best use of relationship context is to compare the current request with the historical pattern, then require extra verification when the pattern breaks. That keeps routine work moving while making impersonation materially harder.

Standards & Framework Alignment

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

MITRE ATT&CK and OWASP API Security Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1078 — Valid AccountsRelationship context helps spot impersonation that precedes account misuse.
Recommendation — Correlate anomalous message patterns with valid-account abuse and investigate the access chain early.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationNormal-looking requests still need explicit permission checks before business actions execute.
Recommendation — Enforce function-level authorization so a plausible request cannot trigger sensitive actions by familiarity alone.
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Relationship context is a supplementary trust signal, not a substitute for authenticating the actor.
Recommendation — Require strong user authentication before accepting requests that change state or move value.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org