security-review-owasp-dotnet-security

Identify .NET security weaknesses across code, configuration, and deployment.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-dotnet-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review-owasp-dotnet-security
Source: https://github.com/sjinks/ai-owasp-skillset/tree/main/.github/skills/security-review-owasp-dotnet-security
Command: npx skills add https://github.com/sjinks/ai-owasp-skillset --skill security-review-owasp-dotnet-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers find .NET security weaknesses caused by unsafe defaults, privilege sprawl, exposed management surfaces, weak isolation, and deployment boundary mistakes.

Core Features & Use Cases

  • Runtime and Privilege Review: Checks service accounts, process privileges, admin paths, and management access for least-privilege failures.
  • Configuration and Dependency Review: Examines tenancy assumptions, hardening settings, secret handling, and third-party trust risks across code and deployment artifacts.
  • Operational Security Review: Evaluates scanning, policy enforcement, rollback readiness, and CI/CD exposure to catch issues that could expand attacker reach.
  • Use Case: Review a .NET microservice to confirm that its container, pipeline, and platform integrations do not expose privileged control planes or cross-tenant access.

Quick Start

Use the security-review-owasp-dotnet-security skill to review the selected .NET service, deployment, or configuration for privilege, isolation, dependency, and management-surface risks.

Frequently Asked Questions about security-review-owasp-dotnet-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review .NET service privilege boundaries and exposed management surfaces?

A .NET security review checks service accounts, process privileges, and admin paths to identify least-privilege failures and exposed management surfaces. It evaluates configuration and operational controls to prevent control-plane compromise across containers and pipelines.

What is the best way to check .NET microservice tenancy isolation and dependency trust?

Checking .NET microservice tenancy isolation involves examining tenancy assumptions, hardening settings, and third-party trust risks across code and deployment artifacts. This identifies weak isolation boundaries and supply-chain risks that could enable tenant escape.

How do I assess .NET deployment hardening and CI/CD pipeline exposure?

Assess .NET deployment hardening by evaluating scanning, policy enforcement, rollback readiness, and CI/CD exposure. This operational security review catches deployment boundary mistakes and pipeline issues that could expand attacker reach into platform integrations.

Can I use OWASP-aligned prioritization for .NET container and platform integration reviews?

Yes, you can apply OWASP-aligned prioritization to .NET container and platform integration reviews. The review focuses on control-plane compromise, tenant escape, and supply-chain risk, requiring evidence-backed findings and explicit documentation of any review gaps.

Why does my .NET security review require evidence-backed findings and explicit review gaps?

A .NET security review requires evidence-backed findings and explicit review gaps to ensure OWASP-aligned prioritization accurately addresses control-plane compromise, tenant escape, and supply-chain risk. This prevents false positives and ensures actionable remediation across services and containers.