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
Re-examination
Verify any fix on demand with targeted re-test probes against the same finding.
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 Re-examination test?
- Verify any fix on demand with targeted re-test probes against the same finding.
- This page is part of Platform under Deliverables.
- 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 a re-examination in Pencheff?
- A re-examination re-runs the specific tests that produced previously reported findings against your updated application. It confirms whether remediation was successful and produces a formal closure certificate that can be submitted as evidence in compliance audits.
- Can Pencheff automatically open pull requests to fix vulnerabilities?
- Yes. For dependency vulnerabilities and some SAST findings, Pencheff can open auto-fix pull requests that bump the affected package to a patched version or apply a known secure code pattern — reviewed and merged by your team.
- How long does a re-examination take?
- A targeted re-examination that re-tests only previously open findings typically completes in 2–10 minutes, depending on the number of findings and the depth of the original test.
Related