Works with the AI Agents you already use
Security Requirements
Turn threats into testable pass or fail security acceptance criteria
$15
Security Requirements
Example session with this skill installed
Using this synthetic threat model, create testable security requirements for a multi tenant application. The identified risks are cross tenant resource access, weak session invalidation after password reset, and sensitive data appearing in application logs. Map applicable requirements to OWASP ASVS 5.0.0, define explicit PASS and FAIL criteria, and preserve traceability to each threat.
- Read your context and instructions
- Compiled the security requirements
Illustrative synthetic demo. It demonstrates the expected requirements structure. No production system, live application, external account, or runtime environment was accessed.
Security Requirements Record
Scope
Synthetic multi tenant application.
Input risks
- Cross tenant resource access
- Session remaining valid after password reset
- Sensitive customer information entering application logs
Requirement SR-01
Security property
Tenant scoped resources must only be accessible to principals authorized for the owning tenant.
Originating risk
Cross tenant resource access
Requirement
Server side resource authorization must verify tenant ownership using trusted authenticated tenant context before a tenant scoped resource is returned or modified.
PASS
A request using a valid principal from Tenant A cannot read or modify a Tenant B resource through identifier substitution or equivalent direct resource access.
FAIL
A valid principal can obtain or modify a resource belonging to another tenant without an explicitly authorized cross tenant capability.
Evidence expected
A negative authorization test using separate tenant identities and known resources.
Framework mapping
Applicable OWASP ASVS 5.0.0 access control requirement or requirements should be recorded during implementation using the exact project approved ASVS reference.
Traceability
Threat T-01: Cross tenant resource access
Requirement SR-02
Security property
A security sensitive credential reset must invalidate sessions that should no longer remain trusted.
Originating risk
Weak session invalidation after password reset
Requirement
After a successful password reset, previously issued sessions that are not explicitly intended to survive the reset must no longer authorize protected actions.
PASS
A session issued before the reset is rejected when reused after the reset according to the documented session policy.
FAIL
A pre reset session continues to authorize protected actions despite the policy requiring invalidation.
Evidence expected
A focused session lifecycle test covering session issuance, password reset, and reuse of the prior session.
Traceability
Threat T-02: Session persistence after credential reset
Requirement SR-03
Security property
Sensitive customer data must not be emitted to application logs unless explicitly required and protected by an approved logging policy.
Originating risk
Sensitive data exposure through logging
Requirement
Application logging must exclude or redact protected customer fields before structured objects, errors, or request context reach logging sinks.
PASS
Representative application flows produce logs without the protected fields defined by the project data classification.
FAIL
A protected field appears unredacted in application logs during an in scope workflow.
Evidence expected
Focused log inspection using synthetic protected values.
Traceability
Threat T-03: Sensitive data in application logs
Requirement Coverage
| Threat | Requirement | Verification status |
|---|---|---|
| T-01 Cross tenant access | SR-01 | NOT YET TESTED |
| T-02 Session persistence | SR-02 | NOT YET TESTED |
| T-03 Sensitive logging | SR-03 | NOT YET TESTED |
Evidence Boundary
These are security requirements and acceptance criteria.
No application control was executed.
No security test was performed.
No PASS result is claimed for the system itself.
Framework mappings must be confirmed against the exact ASVS 5.0.0 control text used by the project before being treated as formal compliance traceability.
Handoff
Route SR-01 through SR-03 to security-testing after implementation evidence is available.
The testing workflow should return PASS, FAIL, or INCONCLUSIVE evidence for each requirement without changing the requirements retrospectively to match the implementation.
Connects securely to your tools. The creator never sees your data.
About this skill
Turns identified threats, project risk, architecture context, and security objectives into explicit requirements that engineering and QA can actually verify. Each requirement defines a security property, measurable acceptance criteria, evidence expectations, and traceability back to the risk it addresses.
What it does
- Converts threat model outputs and project risks into concrete security requirements.
- Replaces vague security guidance with testable acceptance criteria.
- Maps applicable requirements primarily to OWASP ASVS 5.0.0.
- Defines explicit PASS and FAIL conditions for each requirement.
- Records the threat, asset, trust boundary, or risk that justifies each requirement.
- Separates mandatory controls from recommendations and unresolved evidence gaps.
- Defines evidence expectations so later testing knows what must be demonstrated.
- Produces a requirement set suitable for implementation planning, QA, security testing, and release evidence.
How it works
- Risk intake identifies the relevant threats, assets, trust boundaries, abuse cases, and project constraints.
- Security property definition states what must remain true for the system to be considered adequately protected.
- Requirement construction converts each applicable property into a specific and testable statement.
- Framework mapping links requirements primarily to relevant OWASP ASVS 5.0.0 controls when applicable.
- Acceptance criteria define explicit PASS and FAIL conditions.
- Traceability links each requirement back to the originating threat or project risk.
- Evidence planning describes what later review or testing must observe to determine the result.
- Handoff prepares the requirements for implementation and focused security testing.
Boundaries
This skill defines security requirements. It does not prove that those requirements are implemented or satisfied.
System modeling and threat enumeration belong to threat-modeling.
Execution of the resulting verification cases belongs to security-testing.
A final release security decision belongs to security-release-gate.
A confirmed vulnerability requiring a corrective implementation plan belongs to security-remediation-planning.
The skill does not modify application code, configuration, infrastructure, or production systems.
Why this beats prompting it yourself
Generic security requirements often say things such as "use secure authentication," "protect sensitive data," or "follow OWASP best practices." Those statements are difficult to test and provide weak release evidence. This skill converts risk into specific security properties with explicit acceptance conditions and traceability so engineering, QA, and security teams can determine whether each control actually passes.
Frameworks and traceability
OWASP ASVS 5.0.0 is the primary verification structure when applicable. Framework mappings support the requirement but do not replace project specific reasoning. A requirement must still be justified by the system, threat, or risk context supplied to the workflow.
Validation
At pack level, JetFerrari Security Engineering passed 58/58 routing integrity checks with zero unresolved cases.
This skill is also covered by pack level structural, installation, discovery, and behavioral validation. No unsupported individual runtime qualification is claimed here.
Use cases
- Convert a threat model into security acceptance criteria.
- Define testable authentication and authorization requirements.
- Create measurable security requirements before implementation.
- Replace vague security best practices with PASS and FAIL conditions.
- Build traceability between threats, controls, tests, and release evidence.
- Prepare requirements that can be executed by
security-testing.
Known limitations
The quality and completeness of the requirements depend on the threats, architecture, assets, trust boundaries, project constraints, and security context available to the agent. Missing system context can result in requirements remaining conditional or incomplete. Framework mappings do not establish that a control is implemented or effective. This skill defines requirements but does not implement controls, execute security tests, or issue a release verdict.
Part of JetFerrari Security Engineering.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
The quality and completeness of the requirements depend on the threats, architecture, assets, trust boundaries, project constraints, and security context available to the agent. Missing system context can result in requirements remaining conditional or incomplete. Framework mappings do not establish that a control is implemented or effective. This skill defines requirements but does not implement controls, execute security tests, or issue a release verdict.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
Access is limited to threat models, architecture information, security requirements, project documentation, and repository context needed to define testable security criteria. The skill may use local read only inspection commands but does not modify project files, access production systems, retrieve credentials, execute security tests, or issue a release decision.