Trust

Trust starts with proof you can inspect.

See how we test, how we handle evidence, and how your team verifies the fix. From open-source checks to reports for security and compliance reviews, our work is built to be examined.

Inside the evidence packREPORT / 01
Trace every conclusion

A finding you can follow.

Security assessmentScope · evidence · remediation
01What we testedScope recorded
02What we provedEvidence linked
03What to fixTasks defined
04How to verifyRetest criteria
InspectRedacted evidence
VerifyRepeatable checks
Illustrative report structure. Explore the sample for the full format.

External testing

We test from outside the way a customer, attacker, or confused user would. Browser, API, and MCP probes exercise the interfaces your users and agents rely on.

Authorized scope

Audits and authenticated monitoring require customer-approved assets, credentials, rate limits, and excluded actions.

Verified evidence

High-impact audit findings are validated with concise proof. Monitoring alerts include trace context and confidence signals.

Agent-ready remediation

Reports include structured tasks that engineers can hand to AI coding agents with constraints and validation steps.

Layered judgment

Script-first checks, guarded LLM judges, and human calibration reduce false confidence in AI safety scores.

Practical data handling

Evidence is minimized, unnecessary secrets are redacted, and handling and retention requirements are agreed during scoping.

Security evidence for your next review

Built for engineering.
Ready for the compliance conversation.

Give customers, auditors, and your security team a report they can follow: what was tested, what was proven, what to fix, and how the fix was verified.

SOC 2

Customer + auditor evidence

Documented test scope, control observations, risk-ranked findings, remediation tracking, and retest results for your Trust Services Criteria evidence collection.

HIPAA

Security risk analysis support

Technical evidence on access controls, sensitive-data exposure, auditability, and application boundaries to inform your HIPAA Security Rule risk analysis.

PCI DSS

Payment security reviews

Application and API attack paths, authorization checks, and remediation evidence for the payment systems in your agreed scope. Confirm required testing with your QSA.

ISO 27001 + NIST

Risk management support

Findings and corrective actions to support ISO/IEC 27001, NIST CSF, and internal risk registers. Agree any control crosswalk your reviewers need during scoping.

Recognized methods. Traceable coverage.
  • OWASP Top 10
  • OWASP API Top 10
  • OWASP LLM Top 10
  • WSTG / ASVS
  • DAST
  • SAST / SCA
  • CWE / CVSS
  • MITRE ATT&CK

Authenticated dynamic application security testing (DAST) and manual verification anchor our pen tests. The full engagement adds static application security testing (SAST), software composition analysis (SCA), and cloud review with provided access. OWASP categories guide coverage; reports record tested, excluded, and untested areas. Applicable findings include weakness classifications, severity rationale, and attack-technique mapping.

Reports support your compliance program. Certification, SOC 2 attestation, HIPAA compliance determinations, and PCI Approved Scanning Vendor (ASV) scans are separate services. Framework mappings and required test coverage are agreed before testing.

Explore the report evidence pack
Community trust, built in the open

Read the tests.
Run them yourself.

Our free, Apache 2.0 licensed pytest-wardenbot plugin brings adversarial chatbot and agent checks into your own test suite. Inspect the attack corpus, review the grading logic, and contribute a regression case.

Start with prompt injection, jailbreaks, system-prompt leaks, canary tokens, and business facts. For tool-using agents, versioned MCP and application-boundary scenarios record what the agent actually did. Deterministic checks run without an LLM judge; your provider's usage still applies.

pytest-wardenbotApache 2.0
# Install the community plugin
pip install pytest-wardenbot

# Generate your starter tests
pytest --wardenbot-quickstart

# Set your approved chatbot endpoint
export CHATBOT_URL=https://example.com/chat
pytest

Beta software (0.8.0) with a public changelog. A passing test suite provides regression evidence; it does not establish complete security.

Procurement and data handling

Confirm the details your security team needs.

Discuss data handling, retention, subprocessors, and incident contacts during procurement. We confirm available documentation and engagement requirements with your team.

Request security documentation ↗
  • Testing scope, authorization, and rules of engagement
  • Evidence handling, redaction, and retention requirements
  • Data processing and subprocessor documentation available for the engagement
  • Incident contacts, stop procedures, and escalation expectations
  • Report access, delivery, and customer distribution requirements
  • Monitoring cadence, endpoint limits, and usage budgets
Audits

Authorized scope before active tests.

Paid audits require ownership confirmation, approved targets, intensity limits, exclusions, and payment after scope review.

Read rules of engagement
Monitoring

Compatibility and consent before recurring probes.

Monitoring setup confirms bot and MCP endpoints, test credentials, allowed tools, protected facts, alert routes, and recurring test boundaries.

Explore monitoring
Reports

Evidence stays useful and restrained.

Findings and alerts include trace context, impact, remediation guidance, and redaction where sensitive details are not needed for the fix.

View sample report