Frequently Asked Questions
Answers to the questions our clients ask before reaching out.
When should we contact you?
Contact Factero once critical systems are stabilized and basic operations have resumed, even partially. Our intervention takes place in the post-stabilization phase — not during an active incident. That's when structural decisions are made: the post-mortem, fix validation, and the remediation plan. The pressure to 'get back to normal' is intense after an incident, but it's precisely that rush that creates recurrences. Factero structures the post-mortem using the NIST Incident Response framework (Respond and Recover functions), validates that fixes were actually applied — not just promised — and documents everything in a format accepted by cyber insurers and boards of directors. If you're in the middle of an active incident and need immediate emergency response, contact us directly to assess together whether an active-incident intervention is possible.
How does this work with our cyber insurer?
The post-mortem report and fix validation are exactly what a cyber insurer requests after a claim. Factero produces factual, independent documentation — incident timeline, root cause identified using the NIST Incident Response framework, validated fixes, and recommended preventive measures — in a two-level structured format: executive summary for leadership and the insurer, technical detail for the IT team. This independent report can support your claim by demonstrating that concrete corrective measures were taken, documented, and verified by a third party. Our principal associate, CISA-certified (Certified Information Systems Auditor — ISACA), brings the professional credibility insurers expect. We don't make declarations to your insurer on your behalf, but we produce the documentation that lets you do so from a position of strength.
Will the post-mortem identify responsibilities?
The post-mortem identifies what happened and why, not who is to blame. The distinction is fundamental: understanding root cause enables fixing vulnerabilities and preventing recurrence. Looking for blame creates resistance that slows recovery and prevents teams from sharing necessary information. Factero uses a root cause analysis methodology structured according to the NIST-CSF framework (Respond and Recover functions), centered on facts and timeline — not blame attribution. The report documents the sequence of events, exploited vulnerabilities, applied fixes, and recommended preventive measures. If contractual responsibilities need to be established in a legal context — for example, a dispute with an IT provider or an insurance claim — that's a separate engagement under Factero's expert witness service, with a different intervention framework and different obligations.
Our provider says it's fixed. Why validate anyway?
'Fixed' and 'secure' aren't always the same thing. After an incident, the natural priority is to get back to normal as fast as possible. But that urgency creates a concrete risk: some fixes are applied on the surface — symptoms disappear, but root causes remain. Factero independently validates that announced fixes were actually applied, that the root cause was identified and addressed, and that restored systems are in a secure state. This validation follows the NIST Incident Response framework and draws on the expertise of a CISA-certified consultant (Certified Information Systems Auditor — ISACA). The approach isn't a lack of trust in your provider — it's reasonable diligence you owe to your leadership, board of directors, and cyber insurer. If fixes are solid, independent validation confirms it. If a gap exists, you know before a second incident occurs.
What approach do you use for the post-mortem?
Factero structures each post-mortem according to the Respond and Recover functions of the NIST Cybersecurity Framework (NIST-CSF), the international cybersecurity standard. The approach is strictly factual and follows four phases: chronological reconstruction of the incident from logs, testimony, and technical evidence; root cause identification through deep analysis (not symptoms); validation that announced fixes were actually applied and are effective; prioritized recommendations for residual adjustments. The report is structured at two levels: an executive summary for leadership, the board, or the insurer, and a complete technical detail for the IT team or provider. The principal associate holds the CISA certification (Certified Information Systems Auditor) from ISACA, the international reference in information systems auditing. The approach is designed to understand and correct — not to assign blame.