Findings Remediation
We fix the vulnerabilities we find - so you don't have to
What this engagement covers
The service
Most pentest firms hand you a report and walk away. We don't. Our Findings Remediation service pairs you with the same security engineers who performed your assessment. They patch the code, harden the configs, and fix the infrastructure issues - eliminating the gap between knowing about a vulnerability and actually resolving it.
What we test
We remediate all vulnerability classes discovered during penetration testing engagements: code-level fixes for injection flaws, XSS, IDOR, and business logic issues; infrastructure hardening for misconfigurations, weak TLS, open ports, and excessive permissions; cloud remediation for IAM policies, S3 buckets, security groups, and serverless functions; and Active Directory fixes for Kerberoasting, delegation, GPO, and certificate abuse paths.
Scoping & Assessment Depth
Black Box Assessment
Zero-KnowledgeSimulates an external adversary targeting Findings Remediation with no internal credentials, source code, or architecture documentation. Assesses perimeter exposure, unauthenticated attack paths, and edge resilience.
Gray Box Assessment (Recommended)
CredentialedSimulates an authenticated user, tenant, or insider threat within Findings Remediation. We evaluate role segregation, authorization boundaries, privilege escalation, and business logic flaws across user tiers.
White Box / Source-Assisted
Full-KnowledgeConducted with direct access to architecture schematics, configuration files, and API/code documentation. Eliminates blind spots and provides exhaustive coverage of security mechanisms governing Findings Remediation.
Attack Surface & Vulnerability Vectors
Injection flaws (SQL, XSS, command injection)
Rigorous testing and validation to uncover Injection flaws (SQL, XSS, command injection) across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
Broken access control and IDOR
Rigorous testing and validation to uncover Broken access control and IDOR across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
Authentication and session management
Rigorous testing and validation to uncover Authentication and session management across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
Security misconfiguration
Rigorous testing and validation to uncover Security misconfiguration across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
Sensitive data exposure
Rigorous testing and validation to uncover Sensitive data exposure across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
Missing security headers
Rigorous testing and validation to uncover Missing security headers across your Findings Remediation environment. We produce deterministic proof-of-concept exploits to verify exploitability without risking service stability.
How we run it
Our engineers review every finding from your assessment report, triage by risk severity, and create a prioritized remediation plan. We work directly in your codebase and infrastructure - submitting pull requests, applying config changes, and validating each fix before marking it resolved. Every remediation is documented with before/after evidence so your auditors can see exactly what changed.
Review and triage assessment findings by severity
Rigorous technical execution, boundary verification, and manual exploitation testing targeting review and triage assessment findings by severity across your findings remediation deployment.
Reproduce each vulnerability in staging environment
Rigorous technical execution, boundary verification, and manual exploitation testing targeting reproduce each vulnerability in staging environment across your findings remediation deployment.
Develop and test code patches for application flaws
Rigorous technical execution, boundary verification, and manual exploitation testing targeting develop and test code patches for application flaws across your findings remediation deployment.
Apply infrastructure and cloud hardening changes
Rigorous technical execution, boundary verification, and manual exploitation testing targeting apply infrastructure and cloud hardening changes across your findings remediation deployment.
Fix authentication and authorization logic issues
Rigorous technical execution, boundary verification, and manual exploitation testing targeting fix authentication and authorization logic issues across your findings remediation deployment.
Resolve dependency and library vulnerabilities
Rigorous technical execution, boundary verification, and manual exploitation testing targeting resolve dependency and library vulnerabilities across your findings remediation deployment.
Validate each fix eliminates the vulnerability
Rigorous technical execution, boundary verification, and manual exploitation testing targeting validate each fix eliminates the vulnerability across your findings remediation deployment.
Document all changes with audit-ready evidence
Rigorous technical execution, boundary verification, and manual exploitation testing targeting document all changes with audit-ready evidence across your findings remediation deployment.
What you receive
Findings land in your tracker as you go, not only in a PDF at the end. Retest is in scope, not a change order.
- Prioritized remediation plan with timelines
- Code patches submitted as pull requests
- Infrastructure and cloud configuration fixes
- Before/after evidence for every remediation
- Updated risk register with resolved findings
- Remediation summary report for auditors
- Knowledge transfer session for your team
- Post-fix validation testing
What we usually find
The issues this engagement surfaces most often. Yours will differ, but this is the shape of it.
Who this is for
Auditor-Ready Compliance Crosswalk
| Framework | Control Section | Testing Evidence & Report Deliverable |
|---|---|---|
| SOC 2 Type II | CC4.1, CC7.1, CC7.2 | Technical testing evidence validating system boundaries, access restrictions, and vulnerability identification controls. |
| PCI DSS v4.0 | Requirement 11.4 & 11.4.3 | Adversary-driven external and internal penetration testing with application-layer validation and vulnerability remediation verification. |
| HIPAA Security Rule | 45 CFR § 164.308(a)(8) | Formal technical evaluation verifying the integrity of ePHI safeguards, network segmentation, and privileged access safeguards. |
| ISO/IEC 27001:2022 | Control A.8.8 & A.8.20 | Management of technical vulnerabilities and network security verification through independent technical assessments. |
| NIST Cybersecurity Framework | PR.AC, DE.CM, RS.AN | Technical testing verifying access controls, anomaly detection efficacy, and incident response mitigation capabilities. |
| CMMC 2.0 Level 2 / 3 | CA.L2-3.12.1, SC.L2-3.13.1 | Technical validation of Controlled Unclassified Information (CUI) protection, perimeter defense, and enclave isolation. |
Findings are mapped to SOC 2, PCI-DSS, HIPAA, ISO 27001, NIST CSF, CMMC, so the report drops into an audit package rather than needing to be translated first. If you need the readiness work behind one of those, that is a separate engagement.
Frequently Asked Questions
Direct answers on scoping, methodology, compliance validation, and deliverables.
Our Findings Remediation service combines deep manual testing with automated verification. We cover: Prioritized remediation plan with timelines, Code patches submitted as pull requests, Infrastructure and cloud configuration fixes, Before/after evidence for every remediation, Updated risk register with resolved findings. Every engagement includes reproducible proof-of-concept exploits, developer-ready remediation guidance, and a free retest.
Yes. Findings are directly mapped to SOC 2, PCI-DSS, HIPAA, ISO 27001, NIST CSF, CMMC control requirements. The resulting report is auditor-ready and formatted for immediate submission to SOC 2 CPAs, PCI QSAs, and enterprise vendor risk assessment teams.
Yes. Every Lorikeet Security engagement includes free retesting within 30 to 60 days to validate that your remediation patches successfully resolve the identified vulnerabilities before your final report is issued.
Typical active testing turnaround is 1-3 weeks, with critical findings reported immediately via your Talon portal so your engineering team can begin remediation without waiting for the final PDF.
Pricing starts from $5,000. We scope the engagement in one call based on your environment's surface area, user roles, and complexity, providing a transparent, fixed-price quote with no hidden change orders.
Scope it in one call
Tell us what is in scope and we come back with a fixed price and a start date. No discovery-call maze, no hourly estimate that moves.
