testing-application-security

Verifies authorization, session, and input handling of web applications through OWASP-mapped API-level checks.

113|17|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill testing-application-security-jaktestowac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-application-security
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/testing-application-security/skills/testing-application-security
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill testing-application-security-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Functional test suites prove the happy path works for authorized users but rarely verify that the application actually enforces its access control, session, and input-handling claims. This Skill gives testers a systematic, OWASP-informed workflow for security testing at a tester's depth, starting from a mandatory written authorization gate and ending with findings routed through the proper disclosure path. ## Core Features & Use Cases - Authorization Matrix: Builds a complete role-by-endpoint matrix verified at the API level, catching IDOR, horizontal and vertical escalation, method confusion, and mass assignment. - Session and Authentication Checks: Verifies logout invalidation, token rotation, cookie flags, lockout behaviour, and password reset token handling against what the application claims. - Safe Input and Data Exposure Observation: Sends inputs a validator should reject and observes responses for injection indicators, verbose errors, and data leakage, stopping at confirmation rather than exploitation. - Use Case: A new role is added to a multi-tenant SaaS product. Use this Skill to obtain written authorization, build the full role-by-endpoint matrix with synthetic accounts, verify every cell at the API, and report any cross-tenant findings through the security disclosure channel. ## Quick Start Ask the AI to run a security testing pass on your staging application, starting with the authorization gate and building an authorization matrix for all roles and endpoints.

Frequently Asked Questions about testing-application-security

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

FAQPage Schema
How do I test broken access control in a web application?▼

Build an authorization matrix covering every role against every protected endpoint and verify each cell at the API level, not through the UI. Check for IDOR by swapping resource identifiers, test all HTTP methods on each path, and compare observed status codes against expected ones.

How do I check for IDOR vulnerabilities as a tester?▼

Request a resource belonging to one user while authenticated as another user and observe whether the API returns it. Test sequential ids, cross-tenant ids, and indirect paths like nested attachments, stopping after a single demonstration rather than enumerating records.

Can I do security testing without written authorization?▼

No. Testing a system without written authorization naming the system, environment, scope, prohibited actions, time window, and contact is unauthorized access regardless of intent or employment. A bug bounty scope statement counts as authorization only for exactly what it lists.

What is the difference between tester security testing and penetration testing?▼

Tester-scope security testing confirms a class of finding with the minimum demonstration, such as reading one record you should not see, then reports it. Penetration testing develops exploits, chains findings, and covers infrastructure, all of which are handed off to security professionals.

Should security findings go in the public bug tracker?▼

No. A security finding filed publicly is a disclosure. Route findings through the team's documented security disclosure path, a restricted-visibility tracker, or directly to the security owner, with personal data redacted from all evidence.

When should security testing stop and hand off to a specialist?▼

Stop when a response indicates a real injection path, when a finding reaches high severity, or when continuing would require exploit development, chaining, or infrastructure testing. Confirming the vulnerability class is the tester's job; developing it further exceeds the authorized scope.