java-security-audit

Audit Java/Quarkus applications for OWASP Top 10 vulnerabilities and remediation.

1|5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/mdproctor/claude-skills --skill java-security-audit-mdproctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-security-audit
Source: https://github.com/mdproctor/claude-skills/tree/main/java-security-audit
Command: npx skills add https://github.com/mdproctor/claude-skills --skill java-security-audit-mdproctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps security professionals identify vulnerabilities in Java/Quarkus server applications before they reach production, focusing on OWASP Top 10 patterns with language-specific guidance.

Core Features & Use Cases

  • Performs OWASP-aligned security reviews on Java/Quarkus codebases, covering authentication, authorization, input validation, data handling, and configuration hardening.
  • Provides a security audit workflow, severity classifications, reporting formats, and a CI-ready checklist that ties to security-principles and java-dev patterns.
  • Supports targeted reviews of authentication, payment, and PII handling, and can be invoked during pre-production reviews or on-demand for critical subsystems.

Quick Start

Run a security audit on your Quarkus project and report OWASP-aligned findings.

Frequently Asked Questions about java-security-audit

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

FAQPage Schema
How do I perform an OWASP security audit on a Quarkus application?

Run an OWASP security audit on Java Quarkus codebases by evaluating authentication, authorization, input validation, and data handling against OWASP Top 10 patterns to deliver a structured severity report with remediation recommendations.

What is the best way to identify security vulnerabilities in Java server applications?

Identify security vulnerabilities in Java server applications by applying OWASP-aligned security review workflows that analyze codebase patterns, classify severity, and output CI-ready checklists tied to security principles and Java development patterns.

Can I scope a security review to just authentication and PII handling subsystems?

Yes, you can scope security reviews to targeted subsystems like authentication, payment, and PII handling, enabling focused pre-production audits or on-demand risk assessments for critical application features.

Do I need a complete application codebase to run a Java security review?

No, a complete application codebase is not required; you can define the scope of the security review to target specific features or subsystems within your Java or Quarkus application for focused vulnerability identification.

When do I need to run an OWASP vulnerability assessment for my Java codebase?

Run an OWASP vulnerability assessment for your Java codebase during pre-production reviews or on-demand for critical subsystems to identify and remediate security flaws before they reach production deployment.