Framework mapping
MITRE ATT&CK® Enterprise mapping
Tactics: Initial Access
Platforms: Windows, Linux, IaaS, Network Devices, Containers, ESXi
Relationship: application-security context
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.
Related defensive techniques
Inferred and experimental: These relationships are generated from D3FEND graph paths. They are hypotheses for analysis, not proof of prevention, detection, or control effectiveness.
MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation.
What it means
The exact names change across taxonomies, but the underlying issue is how untrusted input, identity, authorization, state, and business logic cross trust boundaries.
Why it matters
Understanding attack classes helps teams design controls and testing strategies that address causes rather than one vulnerable URL.
Practical focus
- Validate authorization on every sensitive action
- Treat all client-controlled input as untrusted
- Protect sessions and state transitions
- Test business logic as well as technical inputs
Common mistakes
- Focusing only on input validation
- Assuming a hidden interface is inaccessible
- Fixing one occurrence without finding the underlying pattern
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: