Reviews code or a system design you own for security weaknesses, including web, API and AI-feature risks, with severity, impact, fixes and how to verify each fix. Use it before a release or a design sign-off.
Groups security scanner alerts and dependency warnings, finds shared root causes, and ranks fixes by severity and exposure. Use it when a long alert list needs a clear remediation order.
Reviews container orchestration manifests or deployment configs for reliability, security and cost problems and returns prioritized fixes with corrected snippets. Use before a production rollout or during a platform audit.
Explains a security finding from a code scanner, fixes it in the context of your code, and proposes tests that prove nothing broke. Use when a scan flags unsafe handling of user input.
Reviews a network design or an outage description and returns risks, a hardening plan and a step-by-step troubleshooting path. Use when designing, auditing or debugging an office, hybrid or cloud network.
Reviews how an organization stores and shares sensitive data and proposes a prioritized protection plan covering access, encryption, sharing rules and monitoring. Use when tightening data handling in a small team.
Designs a tested, low-noise detection rule for a suspicious behavior in your own logs, with false-positive tuning, evasion considerations, a safe test plan and analyst triage steps. Use it for defensive security monitoring.
Maps how a feature or system you own could be attacked or misused and lists prioritized defenses, detection and tests. Use during design or before a security review of your own product.
Engineeringsecurityreview
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.