risk
Applications running with excessive privilege / insecure design
Applications or services running under privileged accounts, opening unnecessary network connections, or lacking secure-by-design architecture mean a single compromise grants broad system access and expands attack surface.
Record JSON · Open in map · Data retrieval guide
Catalog revision: 24028ffcfc2b295fa1b08ee6caa84b765f0731b321496bf4f548c49ad2177028. A connection does not establish full coverage.
Attributes
- category
- cyber_security
- domain
- Secure Development (SDLC) & Application Security
- Secure Configuration & Change Management
- taxonomy
- iso-27005-vulnerability
- inherent_rating
- high
Details
- risk_id
- sdlc-insecure-privileged-apps
- category
- cyber_security
- likelihood
- medium
- impact
- high
- inherent_rating
- high
- treatment
- mitigate
- taxonomies
- iso-27005-vulnerability
Source
No record-specific source URL is provided.
Connections
- UC-SDLC-03 — Define and approve security requirements for applications mitigates Applications running with excessive privilege / insecure design
- strength
- related
- rationale
- Approving authentication/authorization requirements up front constrains later designs away from excessive privilege.
- UC-CONFIG-04 — Build security and privacy into software design and upkeep mitigates Applications running with excessive privilege / insecure design
- strength
- primary
- rationale
- Engineering security from design onward with secure-coding standards is the secure-by-design defense against insecurely designed, over-privileged applications.
- UC-SDLC-04 — Engineer systems with secure architecture and design mitigates Applications running with excessive privilege / insecure design
- strength
- primary
- rationale
- Least privilege, isolation of execution domains and attack-surface minimization directly prevent over-privileged, broadly-exposed applications.
- UC-SDLC-01 — Follow a secure development lifecycle with approval gates mitigates Applications running with excessive privilege / insecure design
- strength
- related
- rationale
- Secure-by-design activities embedded in the lifecycle contribute to eliminating insecure/over-privileged designs, though architecture (UC-04) is the operative control.
- UC-SDLC-08 — Maintain current system documentation and knowledge mitigates Applications running with excessive privilege / insecure design
- strength
- related
- rationale
- Documentation covering secure configuration guides operators away from over-privileged/insecure deployment.