Size and geography point to the first group: companies running networks and offices on several continents will find the deepest benches at LevelBlue, IBM, Deloitte and Verizon. Organizations that want help choosing tools before anyone operates them are better served by Optiv, or by GuidePoint if they would rather outsource one function at a time. The specialists answer narrower needs: Cyderes for identity-driven risk, BlueVoyant for Microsoft shops and supplier monitoring, Rapid7 for vulnerability and application security alongside detection, and Deepwatch for getting more out of an existing SIEM. Whichever you choose, get three things in writing: what your cyber insurer expects of the service, how long it keeps your logs, and what its own audit report covers.
Will an MSSP help us qualify for cyber insurance?
It can, as long as the controls it runs match what you tell the insurer. Underwriters now treat certain controls as a condition of coverage: the broker Marsh lists 12 control categories that insurers commonly require, among them multifactor authentication for remote and administrator access, endpoint detection and response, encrypted and tested backups, privileged access management, patch and vulnerability management, logging and monitoring, and an incident response plan, and an MSSP operates many of them day to day. The application has to be accurate. In 2022, after a ransomware attack, Travelers asked a federal court in Illinois to rescind a cyber policy it had sold to International Control Services, saying the company had attested to multifactor authentication across its systems while using it only on its firewall; the two sides agreed to an order declaring the policy void from its inception. Before each renewal, ask your provider for written evidence of every control it runs and check the application against it.
How long should security logs be kept?
As long as the strictest rule you answer to requires, and the period belongs in the contract rather than in the provider’s default settings. PCI DSS, the card-payment standard, requires at least 12 months of audit log history, with the most recent three months immediately available for analysis; the FBI’s CJIS Security Policy, version 6.1 of June 2026, requires at least one year for organizations handling criminal justice information; and federal agencies following OMB memo M-21-31 keep most log categories for 12 months in active storage plus 18 months in cold storage. HIPAA sets no fixed period for audit logs: HHS declined to specify one in 2003, a January 2025 proposal that is not yet final would require keeping activity records for a period reasonable and appropriate to each type of log, and Security Rule documentation must be kept for six years. Ask how many months stay searchable, what longer storage costs and how you get your logs back if you leave.
What should we look for in an MSSP’s SOC 2 report?
A SOC 2 report is a CPA firm’s examination of a service provider’s controls against the AICPA’s criteria for security, availability, processing integrity, confidentiality and privacy. Ask for a Type 2 report: a Type 1 judges only whether controls were suitably designed as of a single date, while a Type 2 also tests whether they operated effectively over a period and describes the auditor’s tests and results. There is no required minimum period, so check that the window is long enough to be meaningful, read any exceptions the auditor found and see which of the five categories are covered. Also read the complementary user entity controls, the steps the provider assumes you will take yourself, such as managing your own administrator accounts, because its controls only work if you do your part. The AICPA proposed updated criteria in October 2026, with comments due January 15, 2027.