How can public employee information support impersonation?
A human attack surface includes publicly discoverable details and business relationships that could help someone reach or impersonate staff. Connect that exposure to specific requests and verification procedures rather than assuming it proves compromise.
What can someone learn before contacting your staff?
A public biography can reveal an employee’s role. A conference agenda can identify the team they lead. A supplier announcement can explain which project gives an unexpected caller a plausible reason to make contact.
Individually, those facts may be ordinary business information. Combined, they can help someone impersonate a colleague, choose a convincing request, or find the person who handles an exception. Ask whether any of your approval processes would accept those facts as proof of who is calling or permission to act on the request.
MITRE ATT&CK documents adversaries gathering employee names, email addresses, credentials, and other identity information for targeting. Sources can include public websites and social media, as well as information obtained through other methods. Public exposure is one input to an attack, not proof that an employee has been targeted or compromised. MITRE: Gather Victim Identity Information
Start with the decision an attacker would want
A list of names tells a security team little about what to fix. Start with a sensitive workflow: account recovery, supplier changes, external document release, or contractor access. Identify who receives the request, who can approve it, and which details the procedure treats as evidence.
Then examine what an outsider could plausibly know. Could a caller name the manager and current project? Does a public case study identify the supplier that handles a critical service? Would those details help the caller locate the right team, or would staff accept them as sufficient verification?
The distinction matters. In Microsoft’s October 2023 Octo Tempest report, operators impersonated newly hired employees and persuaded technical administrators to reset passwords or MFA methods. Microsoft described the approach as blending into onboarding processes. The relevant defensive question is what the help desk required beyond a believable employee story. Microsoft: Octo Tempest initial access
Our new-hire impersonation guide follows that question through the relationship, requester, and access decision. Public research may help an attacker tell the story; the recovery procedure determines whether the story can authorize a change.
Connect public information to the job
A human attack surface includes publicly discoverable details and business relationships that could help someone reach or impersonate staff. It includes more than executive biographies. Reception, help desks, finance teams, and project coordinators all handle requests whose legitimacy depends on context.
Connect the public information to the employee’s actual responsibility, then examine the independent evidence required before they act. A job title alone cannot tell the reviewer which requests that person receives or authorizes.
Keep observation separate from inference. A biography may name a role without identifying current permissions. A public address pattern may suggest an email address without confirming that the mailbox exists. A published partnership may establish a business relationship without explaining who approves payments.
The organization is usually better placed than an outsider to resolve those gaps. Use internal owners to validate the workflow instead of treating public research as a complete map of access.
Do not make verification depend on public facts staying secret
A published supplier relationship can give a caller context for a payment-destination request. The reviewer still needs an independently established supplier contact and the required internal approval. If staff accept the supplier’s name and a manager’s name instead, the verification check needs work; those names were already public.
Our supplier bank-detail review separates contact verification, the record change, and payment approval.
This also helps choose a repair. Remove unnecessarily exposed operational details when the information owner agrees. Where information has a legitimate public purpose, make sure the relevant approval process does not depend on its secrecy.
Collect only what the review needs
A workforce-exposure review should have an agreed purpose, scope, access restrictions, and retention plan. Limit collection to facts needed to evaluate the selected workflow. Avoid turning a security assessment into a broadly circulated dossier of personal information.
Give employees and business owners a way to correct stale or mistaken conclusions. A job title may have changed. A public contact may belong to a shared team. An apparent reporting line may be an inference rather than a published fact. Preserve the source and review date so those distinctions remain visible.
Do not rank employees as inherently vulnerable because they speak at events or maintain a professional profile. Evaluate the request they might receive, the authority it seeks, and the controls available to them. Public engagement can serve the business; look for unnecessary disclosures and checks that treat public knowledge as identity verification or approval.
Check whether public facts can pass verification
Choose one workflow and ask its owner which facts a requester must establish. Compare that requirement with what the public review found. If readily available information would satisfy the check, investigate whether the procedure needs stronger evidence or a separate approval.
An authorized simulation can then test a specific question: will a realistic request reach the required independent verifier? Keep the observation narrow. A convincing story, a completed verification, and a granted account change are different outcomes.
The next article in the series considers how threat reporting can guide scenario selection. Exposure research helps explain which stories are plausible; the assessment must still establish whether the relevant control works.


