security

Identify and remediate API security risks across authentication, authorization, and data handling.

Updated Feb 6, 2026

Search Tags:#authorization #OWASP #authentication #risk-assessment #api-security #vulnerability-detection #secure-by-default

Ready to run

npx skills add https://github.com/pointware/custom-marketplace --skill security-pointware

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/pointware/custom-marketplace/tree/main/claude-plugins/api-guardian/skills/security
Command: npx skills add https://github.com/pointware/custom-marketplace --skill security-pointware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API security is complex and often under-implemented, leaving systems vulnerable to attacks, unauthorized access, and data leaks.

Core Features & Use Cases

OWASP-aligned security guidance for authentication, authorization, input validation, and secure error handling.
Threat modeling and risk assessment for API endpoints, microservices, and gateways.
Practical remediation steps and measurable security controls for teams building or auditing APIs.

Quick Start

To begin, ask the AI to review your API authentication and authorization design and produce a prioritized hardening plan.

Frequently Asked Questions about security

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

FAQPage Schema

How do I identify and fix API authentication and authorization vulnerabilities?▼

API authentication and authorization vulnerabilities expose systems to unauthorized access. This Skill identifies gaps in credential handling, token validation, and permission enforcement across your endpoints, then provides prioritized remediation steps aligned with OWASP Top 10 standards to enforce least privilege and strong authentication controls.

What OWASP security controls should I implement for microservices and API gateways?▼

OWASP-aligned controls for microservices include strong authentication, input validation, secure error handling, and continuous monitoring. This Skill maps threat vectors to specific security requirements for API endpoints and gateways, delivering measurable controls and secure-by-default configurations tailored to your architecture.

How do I conduct threat modeling and risk assessment for my APIs?▼

Threat modeling identifies attack paths and data exposure risks in API designs. This Skill performs risk assessment across authentication, authorization, and data handling layers, helping you prioritize vulnerabilities and build hardening plans with concrete security controls for your endpoints and microservices.

Can I use this guidance to audit existing API implementations?▼

Yes. This Skill reviews API authentication and authorization design, validates data handling practices, and checks alignment with OWASP Top 10 principles. It works with API implementations, microservices, and gateway proxies at any stage—greenfield or legacy—to produce actionable hardening recommendations.

What's the difference between secure-by-default API design and post-deployment hardening?▼

Secure-by-default embeds security controls into architecture and implementation from the start, reducing attack surface. This Skill specifies secure-by-default requirements for authentication, input validation, logging, and monitoring alongside remediation steps for existing systems, helping teams shift left on security.

Do I need security expertise to apply this guidance to my API stack?▼

This Skill translates OWASP principles into practical steps and measurable controls, making it accessible to teams without dedicated security roles. It provides threat modeling frameworks, requirement specifications for least privilege and strong authentication, and prioritized remediation guidance suited to your API architecture.