Framework mapping
MITRE ATT&CK® Enterprise mapping
Tactics: Initial Access
Platforms: Windows, Linux, macOS, Office Suite
Relationship: direct behavior coverage
Open the official ATT&CK object ↗Editorial mapping of an inherited BMC article to related Enterprise ATT&CK behavior, control, evidence, architecture, or risk context. Mapping roles state the relationship and do not assert equivalence unless labeled direct.
MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Bare Metal Cyber is not affiliated with or endorsed by MITRE.
What it means
Campaigns range from broad email lures to carefully researched spear phishing, business email compromise, text messages, voice calls, and collaboration-platform abuse.
Why it matters
Phishing targets both human judgment and technical trust, making layered prevention, detection, reporting, and response necessary.
Practical focus
- Verify unusual requests through a separate channel
- Use strong email authentication and filtering
- Make reporting simple and nonpunitive
- Protect high-value actions with independent approval
Common mistakes
- Teaching users to rely on grammar alone
- Assuming an internal-looking message is trusted
- Focusing only on malicious links while ignoring payment and approval fraud
BMC v0.2.2 cornerstone expansion
Start analysis of Phishing with the mission or business outcome, then identify assets, identities, data, trust boundaries, dependencies, expected behavior, and credible failure or abuse cases.
Translate those observations into preventive, detective, responsive, and recovery controls. A mature explanation states not only what the concept is, but also how a practitioner demonstrates that it is working under normal, abnormal, and recovery conditions.
Evidence of effective implementation
- Documented ownership, scope, decision criteria, and permitted exceptions.
- Configuration or architectural evidence tied to a clear control objective.
- Operational telemetry showing expected and unexpected behavior.
- Testing that covers normal use, abuse cases, failure, rollback, and recovery.
- Exceptions that are approved, time bounded, monitored, and revisited.
- Lessons learned that result in updated designs, procedures, detections, or training.
Questions for learners
- Which security properties and business outcomes does Phishing support?
- What assumptions must remain true for the control or process to work safely?
- What could an attacker, insider, failure, or design error do at each trust boundary?
- Which evidence would prove that controls work continuously rather than only on paper?
- How would the organization respond, restore service, and re-establish trust after failure?
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: