When AI finds the weakness
Check, fix and prove the security of your websites and applications after an alert, with owner acceptance criteria, 3 checklists and 9 templates.
- A first-hour triage and severity levels that turn a headline into owned decisions
- Step-by-step PHP2Shell fixes for managed hosting and for your own servers
- What to do about curl, the LiteLLM package compromise and AI agent access
- Owner acceptance criteria, 3 checklists and 9 templates, also in Word and Excel
- Business owners
- IT and operations managers
- Engineering and platform teams
- Security and incident leads
Three things the handbook gives you
Written from the work we have done, not from vendor brochures.
Classify before you act
A runtime flaw, a library flaw, a malicious package and exposed credentials each close differently. The handbook shows how to tell them apart, find what you actually run and set a severity level from evidence, not headlines.
Fix it and prove it is running
Two procedures, one for managed hosting and one for your own servers and containers, end with the same test: the corrected build is running on every worker, and the business journeys still work.
Close the work with evidence
Owner acceptance criteria for every stage, a RACI, and 12 checklists and templates, from the hosting provider questions to the post-incident review. Editable Word and Excel copies are in the download.
Goes with this handbook
- Cloud and modernization
Cloud migration and modernization
Plan the upgrade, move and harden your systems, and keep them patched without stopping the business.
See Cloud and modernization
Exploring AI? Start with a clearer picture.
Assess your organization’s readiness, understand the gaps that need attention and get a report to discuss with your team.
Free assessment and report. No sales meeting required. Marketing updates are optional.
- Strategy and ownershipReady
- Data and systemsDeveloping
- Skills and adoptionDeveloping
- GovernanceGap
