28 Oct 20265 minutes read
Waseem OsmanDMARC PractitionerSocial Engineering Attacks Begin with Social Media Reconnaissance

Social engineering attacks overview:
- Social media reconnaissance gives attackers what they need to impersonate someone your employees trust.
- Training can’t reliably catch a convincing spoof, but p=reject blocks emails that fail authentication.
- Lookalike domains, display-name spoofing, and compromised mailboxes fall outside what DMARC covers.
- Attackers can query your DNS, and settings like p=none and
+allleave your domain open to spoofing. - Reach p=reject in stages, then keep monitoring for new senders and lookalike domains.
Social engineering attacks start with research, and most of it is free. Attackers read LinkedIn profiles, job listings, and team announcements to learn who holds which role, who reports to whom, and which tools finance uses.
Attackers use social media reconnaissance to gather those details, then write emails that appear to come from an executive or colleague your employees already trust.
The financial impact is measurable. The FBI’s 2025 Internet Crime Report recorded 24,768 business email compromise (BEC) complaints and almost $3.05 billion in reported losses. Awareness training helps, but it can’t reliably stop a spoofed message that looks authentic. Full DMARC enforcement can, because it blocks email that fails authentication before it reaches an inbox.
Check how exposed your domain is to impersonation with Sendmarc’s free domain checker, which returns impersonation, privacy, and branding ratings for your domain in under a minute.
If you're at risk of impersonation, one of our experts will be in touch to assist.
How Social Media Reconnaissance Powers Social Engineering Attacks
Open-source intelligence (OSINT) is the process of collecting and analyzing information from public sources. In social engineering attacks, OSINT is the research phase. The MITRE ATT&CK framework lists searching social media as a reconnaissance technique, noting that these sites can contain company announcements and details about the roles, locations, and interests of staff.
Consider an attacker who wants a fraudulent payment from your finance team. On LinkedIn, they find the CFO, who can approve payments, and an accounts payable (AP) employee, who processes them. One published email address, such as [email protected], shows how your organization formats addresses.
The attacker then writes to the AP manager from what looks like the CFO’s exact address. The message names the right ERP platform and asks for an urgent payment to a new vendor account. Nothing in the email looks wrong because the attacker already did their research.
Which Roles Social Engineering Attacks Target First
Social media reconnaissance ranks employees by their access to money, data, or authority. These roles are targeted most often in social engineering attacks:
- Finance and accounts payable. BEC schemes tend to center on payment requests, so these teams are the most direct route to a fraudulent transfer.
- HR and payroll. A spoofed employee request to change direct deposit details needs only a name and a plausible address.
- IT and security. An email that appears to come from IT or security and tells staff to verify or reset their password gives an attacker a route to credentials.
- Executive assistants. Assistants routinely carry out requests on an executive's behalf, such as sharing documents or arranging payments, so an email that appears to come from the executive can trigger those actions.
How Email Authentication Verifies the Sender
An attacker’s social media reconnaissance can reveal a name, a job title, and a writing style. It can’t prove that a message came from your infrastructure.
- SPF lists the servers authorized to send email on behalf of your domain. An attacker’s server isn’t on that list.
- DKIM signs outbound messages with a private key. Receiving servers verify the signature against the public key in your DNS, and an attacker doesn’t hold your private key.
- DMARC requires SPF or DKIM to pass and align with the visible “From” domain. It tells receivers to monitor (p=none), quarantine, or reject messages that fail.
Full DMARC enforcement blocks unauthenticated email that uses your exact domain. It doesn’t stop display-name spoofing, emails from lookalike domains, or messages sent from a compromised mailbox. Social engineering attacks that rely on those methods need separate controls.
Social Engineering Attacks and Your Authentication Settings
Social media reconnaissance maps your people. Attackers research your domain's technical setup as well.
Attackers can query your DNS records with free tools to see whether your domain enforces DMARC and how your SPF record is configured. A domain at p=none reports failures but doesn’t block them. That gives visibility, not protection.
Common settings that leave a domain open to spoofing include:
- An SPF record ending in
+all, which authorizes any sender - Subdomains set to
sp=none, which lets spoofed emails through - Legacy or parked domains with no DMARC record or a p=none policy
- Unapproved sending tools which delay enforcement
How to Defend Against Social Engineering Attacks
Moving to p=reject without a complete sender inventory risks blocking billing, notifications, and marketing email.
Work in this order:
- Audit all domains and subdomains, including those inherited through mergers and acquisitions
- Map every sending source, internal and third-party, against your SPF and DKIM configurations
- Fix authentication failures for legitimate senders
- Advance the DMARC policy in stages from p=none to p=quarantine to p=reject
- Monitor continuously for new senders, policy changes, and newly registered lookalike domains
How Sendmarc Can Help Reduce the Risk of Social Engineering Attacks
Security and IT teams that manage many domains rarely have spare capacity for the report analysis and DNS changes that enforcement requires. Sendmarc's implementation team takes on that work, moving your company from p=none to p=reject in stages so critical communications keep flowing.
The Sendmarc Platform gives you unified visibility across your domains and sending tools, so you can address shadow IT before it breaks authentication. After enforcement, ongoing monitoring and optimization keep protection current as vendors change.
Social engineering attacks built on social media reconnaissance don’t always use your exact domain. Lookalike Domain Defense monitors for domains that resemble yours and notifies you when new ones appear. Breach Detection monitors sources, including the dark web, for compromised credentials and notifies you when it finds them.
For audit and risk committees, Sendmarc provides audit-friendly reporting and a DMARC compliance certificate as verifiable proof of enforcement status.
Explore how Sendmarc’s DMARC enterprise service brings multi-domain environments to p=reject with centralized visibility, audit-friendly reporting, and ongoing monitoring.


