Failure Patterns, Contracts and Official Sources

Why managed security engagements disappoint, the SLA and contract terms that matter, hidden costs, legal authorisation for pen tests, sector rules and official sources.

Most disappointments with managed security follow a few patterns: half the devices were never onboarded, alerts went to an inbox nobody read, the SLA promised a response but not containment, logs were kept for 30 days when CERT-In expects 180, and the contract made leaving slow. These guides describe those patterns generically, without naming companies.

Start with why managed security engagements fail, which links to every guide in this section. The others cover SLA and contract questions, hidden costs, legal authorisation and scope letters for penetration tests, sector rules from RBI and SEBI, and a list of official sources.

This is general information, not legal advice. For regulated entities, large contracts or an incident in progress, consult a lawyer or a qualified security professional, and report incidents to CERT-In as the Directions require.

Failure Patterns, Contracts and Official Sources

Guides in this topic