dotnet-webapi

Pass

Audited by Gen Agent Trust Hub on Apr 20, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill follows established security best practices for ASP.NET Core development.
  • [SAFE]: Authentication and Authorization patterns use standard ASP.NET Core Identity and JWT Bearer implementations with appropriate security parameters (e.g., ValidateIssuer, ValidateAudience, ValidateLifetime).
  • [SAFE]: CORS implementation explicitly warns against insecure configurations like combining .AllowAnyOrigin() with .AllowCredentials().
  • [SAFE]: Rate limiting instructions include partitioning by user or IP address to prevent denial-of-service and brute-force attacks on sensitive endpoints like login.
  • [SAFE]: Structured logging advice correctly emphasizes using message templates instead of string interpolation to prevent log injection vulnerabilities.
  • [SAFE]: Outbound HTTP calls use standard resilience handlers (retries, circuit breakers) via Microsoft's resilience libraries.
  • [SAFE]: Data access patterns leverage Entity Framework Core with a clear separation of concerns, and health checks include database connectivity verification.
Audit Metadata
Risk Level
SAFE
Analyzed
Apr 20, 2026, 05:28 PM