Run web, API, code, dependency, cloud, AI, and internal-network assessments from one queue with unified findings, evidence, remediation, and audit output.
Risk, reporting, and compliance
Engagement profiles
Quick, Standard, Deep, Red-Team, AI-Only, Compliance, CI, and Continuous modes.
Findings, reports, dashboards, exports, integrations, and retests all read from the same normalized record.
Pencheff favors repeatable checks, then uses AI for triage, enrichment, orchestration, and remediation where it adds signal.
Coverage
What does Engagement profiles test?
- Quick, Standard, Deep, Red-Team, AI-Only, Compliance, CI, and Continuous modes.
- This page is part of Platform under Operational Core.
- It links back into the broader a complete adversarial security platform experience.
- Executive dashboard, letter grade, risk trends, severity rollups, and portfolio posture.
- Technical dossier with findings, reproduction, affected components, remediation, evidence, and re-examination state.
- Compliance mapping for OWASP, PCI DSS, SOC 2, NIST, ISO 27001, HIPAA, OWASP LLM, MITRE ATLAS, NIST AI RMF, EU AI Act, and GDPR.
- Threat modeling with STRIDE, DREAD, attack trees, abuse cases, mitigations, and scan context.
- Unified findings stream, AI triage, advisory enrichment, comments, suppressions, and audit appendices.
Execution
How does Pencheff run this?
- Collect findings from runtime, repo, supply chain, infrastructure, AI, and manual sources.
- Normalize severity, confidence, category, exploitability, reachability, and owner state.
- Generate executive, engineering, compliance, or retest views from the same source record.
- Track suppression, comments, fixes, re-examinations, and residual risk across scan history.
- Export reports and feed integrations without losing the underlying evidence chain.
Evidence
What evidence does this produce?
- Executive summaries, trend charts, severity counts, grade drivers, and business impact language.
- Technical evidence, scanner provenance, reproduction steps, remediation, and references.
- Framework control mappings and audit appendix entries tied to actual findings.
- Retest and verification history for closure and residual risk decisions.
Controls
How is this kept safe to run?
- Compliance rollups are deterministic and recomputed from finding state.
- Triage output distinguishes verified facts from advisory context.
- Reports inherit the same authorization and workspace boundaries as scans.
- Executives and auditors can read summaries while engineers keep deep evidence.
Documentation
Read the full reference.
FAQ
Common questions
- What is an engagement profile in Pencheff?
- An engagement profile is a pre-configured scan template that controls scope, depth, test modules, authentication settings, rate limits, and compliance mappings for a specific type of assessment — such as a quick surface scan, a deep API pentest, or a CI/CD gate check.
- Can I create custom engagement profiles for my team?
- Yes. You can define, save, and share custom profiles with your workspace. Profiles can specify which vulnerability classes to test, set exclusion rules for sensitive endpoints, and configure rate limits appropriate for your application's production environment.
- What is the difference between Quick, Standard, and Deep profiles?
- Quick (2–5 min) runs high-confidence, low-noise checks against the primary surface. Standard (10–25 min) adds broader injection coverage and access-control probes. Deep (30–90 min) enables full exploit chaining, authenticated session testing, and all OWASP Top 10 modules.
Related