Cybersecurity
Remediation and validation
A closed ticket is not a fixed vulnerability. We work with your engineers to apply fixes properly, then retest so you can show each finding is actually resolved.
The problem this service solves
After a test, the report lands and the work stalls. Developers want clearer reproduction steps. Operations teams are unsure of the safest fix. Some findings get patched in the wrong place, or fixed in one location and left in four others. Months later, nobody can say what is truly resolved.
This service handles the stretch between the report and a verified fix. We run walkthroughs, review proposed changes and test the result.
What is in scope
-
Finding walkthroughs
Live sessions with developers and administrators to reproduce each issue and discuss options.
-
Fix design
Help choose between quick mitigations and root-cause fixes, and document trade-offs.
-
Change review
Review pull requests, configuration changes or infrastructure code that address findings.
-
Secure coding guidance
Patterns and libraries that address a class of flaw, not only the single instance.
-
Retesting
Re-run the original test for each finding, and look for variants.
-
Regression checks
Suggest automated tests so the flaw does not return.
How the work runs
Triage
Agree what to fix and in what order.
-
1
Finding review
Confirm each finding’s status, dependencies and owner.
-
2
Plan
Sequence fixes to close the highest-risk paths first.
Fix with engineers
Work alongside the team.
-
3
Walkthrough sessions
Reproduce and explain each issue.
-
4
Fix review
Review proposed changes before deployment.
Validate
Prove it.
-
5
Retest
Run the original attack against the fixed system and test close variants.
-
6
Retest report
Each finding marked fixed, partially fixed or open, with evidence.
What you receive
- Remediation plan with sequence and owners
- Fix review notes
- Retest report with per-finding status and evidence
- Suggested regression tests
- Updated executive summary reflecting closed findings
Tooling and technique
Tool categories describe how we work. They are not a claim of vendor partnership or certification.
Before we start
What we need from you
- The original report and any supporting evidence
- Access to the fixed environment
- Developer or administrator time for walkthroughs
What this service is not
- Writing your application code (we can provide engineers through our staffing practice)
- Closing findings without retesting
What changes afterwards
- Findings are closed at the root cause
- You can show customers and auditors verified fixes
- Recurring flaw classes are reduced
Questions people ask
Can you retest findings from another firm’s report?
Yes, if the report gives enough detail to reproduce the issue. Where it does not, we say so and agree an approach.
How soon after fixes should we retest?
As soon as the fix is deployed to the environment being tested. We agree retest terms, including how many rounds, when we scope the original work.
Related
-
Penetration testing
Authorized, manual testing of applications, networks, cloud and identities to show what an attacker could reach and what to fix first.
-
Enterprise vulnerability management
Design and run a vulnerability management program: ownership, prioritization rules, ticket routing, exceptions and measurement.
-
Security engineering and implementation
Hands-on delivery of security controls and platforms: design, deploy, integrate, migrate, test and hand over.
Need to understand your security exposure?
Speak with a security expert
Talk through your environment and goals. We reply to scope the work before anything is tested.
Speak with a security expertPlan an assessment
Answer a few questions and get a structured preliminary scope you can send us.
Use the plannerUnder attack right now?
Call the US office and tell us what you are seeing. Do not wait for a form reply.
Incident response