Owasp Infrastructure
MicrosoftOfficialPublished by Microsoft
- Skill
- Guidelines
- Security
- CC-BY-SA-4.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The OWASP Infrastructure Top 10 skill provides a machine-readable reference for the 2024 OWASP Infrastructure Security Top 10. It is designed to assist agents in evaluating internal IT infrastructure against common security risks. Each of the ten identified vulnerabilities is documented with a standardized structure, including descriptions, risk assessments, checklists, prevention controls, attack scenarios, detection guidance, and remediation steps.
What it does
- Provides structured access to the OWASP Infrastructure Security Top 10 (2024) vulnerabilities.
- Offers checklists to identify potential security exposures in internal infrastructure.
- Outlines specific prevention controls and defensive measures for each risk category.
- Includes realistic attack scenarios to illustrate how vulnerabilities are exploited.
- Provides actionable detection guidance and remediation steps for security teams.
- Categorizes infrastructure risks into areas like patch management, access control, and data protection.
When to use it
- When performing a security audit of internal IT infrastructure.
- When establishing or improving an infrastructure security management process.
- When assessing the risk profile of existing software and system configurations.
- When training teams on common infrastructure security vulnerabilities and mitigation strategies.
Advantages
- Standardized format allows for consistent evaluation of security risks.
- Derived from authoritative OWASP Foundation content.
- Provides both high-level guidance and specific remediation actions.
- Covers a broad spectrum of infrastructure concerns from credential hygiene to asset management.
Usage examples
- “What are the risks associated with outdated software in our infrastructure?”
- The agent retrieves the ISR01:2024 reference, detailing risks like system compromise, lack of vendor support, and the ease of exploiting known vulnerabilities.
- “How can I detect insecure network access management?”
- The agent provides the detection guidance from the ISR06:2024 document, suggesting methods to identify misconfigured network access controls.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/owasp-infrastructure/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip owasp-infrastructure.zip -d .agents/skills
Documentation by Microsoft
OWASP® Infrastructure Top 10 — Skill Entry
This SKILL.md is the entrypoint for the OWASP Infrastructure Top 10 skill.
The skill encodes the OWASP Infrastructure Security Top 10 (2024) as structured, machine-readable references that an agent can query to identify, assess, and remediate infrastructure security risks.
Normative references (Infrastructure Top 10)
Skill layout
SKILL.md— this file (skill entrypoint).references/— the Infrastructure Top 10 normative documents.00-vulnerability-index.md— index of all vulnerability identifiers, categories, and cross-references.01through10— one document per vulnerability aligned with OWASP Infrastructure Security numbering.
Third-Party Attribution
Copyright © OWASP Foundation. OWASP® Infrastructure Security Top 10 content is derived from works by the OWASP Foundation, licensed under CC BY-SA 4.0 (https://creativecommons.org/licenses/by-sa/4.0/). Source: https://owasp.org/www-project-top-10-infrastructure-security-risks/ Modifications: Vulnerability descriptions restructured into agent-consumable reference documents with added detection and remediation guidance. OWASP® is a registered trademark of the OWASP Foundation. Use does not imply endorsement.
Files
- ATTRIBUTION.mdAdded by AutoGineer995 B
- LICENSEAdded by AutoGineer17.9 KiB
- SKILL.md2.8 KiB
- references/00-vulnerability-index.md2.8 KiB
- references/01-outdated-software.md3.8 KiB
- references/02-insufficient-threat-detection.md4.5 KiB
- references/03-insecure-configurations.md3.9 KiB
- references/04-insecure-resource-user-management.md4.7 KiB
- references/05-insecure-use-of-cryptography.md4.6 KiB
- references/06-insecure-network-access-management.md4.6 KiB
- references/07-insecure-authentication-default-credentials.md3.7 KiB
- references/08-information-leakage.md3.9 KiB
- references/09-insecure-access-resources-management-components.md4.5 KiB
- references/10-insufficient-asset-management-documentation.md4.5 KiB
references/06-insecure-network-access-management.md
title: 'ISR06: Insecure Network Access Management' description: OWASP Infrastructure Top 10 reference for network access management vulnerabilities including flat networks and missing segmentation
06 Insecure Network Access Management
Identifier: ISR06:2024 Category: Network Security
Description
Network Access Management is a fundamental aspect of internal infrastructure architecture and access control regulation. Qualitative Network Access Management prevents a variety of attacks and can reduce the impact of cyberattacks as well as the movement of threat actors inside the internal infrastructure. A critical risk is the lack of network separation, which would restrict access from one part of the infrastructure to another. Organizations often fail to prevent threat actors from accessing the internal network when the attacker gains physical access to a network port or nearby Wi-Fi. Traffic should be supervised and regulated context-based, close to the application layers, for communication paths that must be allowed.
Risk
Absence of network separation severely increases the risk of cyberattacks spreading through the internal infrastructure and compromising the entire environment from a single compromised component.
Without Network Access Control (NAC), an attacker who gains physical access to network components, convinces employees to plug in malicious devices, or reaches nearby Wi-Fi can access internal networks.
Insufficient access regulation at the application layer allows threat actors to abuse commonly allowed communication paths.
Vulnerability checklist
No network separation exists between distinct infrastructure segments.
No Network Access Control (NAC) mechanisms (e.g., certificate-based NAC) are implemented.
Communication paths between network segments are not dynamically regulated at the application layer.
Remote access is not secured with technologies like VPNs.
No access matrix exists to plan and enforce network access management.
Prevention controls
Implement NAC mechanisms (e.g., certificate-based NAC) to ensure only approved devices can access the company network.
Design network separation in the architecture phase; keep network segments as small as possible following the need-to-know principle.
Use VLANs to separate the infrastructure.
Supervise and regulate communication paths between isolated network segments.
Dynamically regulate bridges and network transitions based on application layer context.
Secure remote access using VPN technologies.
Develop an access matrix to plan the network access management structure.
Example attack scenarios
Scenario A — Insufficient network separation
A company hosts different customer-facing applications accessible online. Multiple database servers hold data for those applications, alongside servers for internal applications and data. A threat actor finds a vulnerability in one publicly accessible application server and gains complete control. Because of absent network separation, the attacker moves laterally and compromises all database servers as well as internal application and data servers from a single entry point. The exfiltrated data is later sold to other cybercriminals.
Scenario B — Missing NAC allowing rogue device
A company uses a common internal infrastructure with application servers and employee file shares. New network printers are ordered to replace old ones. A threat actor injects malicious hardware into a new printer before it arrives at the company. When the printer is connected to the internal network, the embedded small computer also gains network access because no NAC is in place. The malicious hardware connects to a remote host controlled by the threat actor, establishing a pivot point into the internal network for additional attacks.
Detection guidance
Audit network topology for missing segmentation between operational zones.
Check for NAC enforcement on all physical and wireless network ports.
Monitor for unauthorized or unknown devices appearing on the network.
Review application-layer traffic controls at segment boundaries.
Remediation
Implement network segmentation with VLANs and firewall rules between operational zones.
Deploy certificate-based NAC on all network ports and wireless access points.
Create and enforce an access matrix governing inter-segment communication.
Implement dynamic application-layer filtering at network boundaries.
Secure all remote access channels with VPN or equivalent encrypted tunneling.
Conduct regular network topology reviews and penetration tests.
Requirements and compatibility
Written for: GitHub Copilot, Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/hve-core · .github/skills/security/owasp-infrastructure · commit f425e94
- Licence
- Creative Commons Attribution-ShareAlike 4.0 International (redistribution allowed)
- LICENSE (written by AutoGineer)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download owasp-infrastructure.zip