Incident Lake

ITIL 4 COVERAGE

Incident Lake coverage, mapped to ITIL 4 practices

Incident Lake sits next to your service desk, not in place of it. It goes deep on incident, problem and knowledge management, ships with a built-in CMDB, and pulls changes and releases from GitHub (or lets you log them by hand) so the deploy that preceded an outage is on the same screen as the incident. Here is how each ITIL 4 practice maps to the product.

Coverage: ◎ Core (in depth) ○ Supported Integrated: delivered together with your existing ITSM or external tools

Practice
Coverage
How Incident Lake delivers it
Incident Management​
◎
Impact-and-urgency priority suggestions, time-based escalation, roles and a running timeline. The agent can propose declaring a major incident; a person confirms it before the SOP and stakeholder notifications kick in.
Problem Management​
◎
Record root causes, workarounds, and permanent fixes across a lifecycle that runs through to known error. AI surfaces recurring similar incidents as problem candidates.
Knowledge Management​
◎
Articles, runbooks, known errors, and FAQs in one place. AI drafts articles from incident reports and known errors, and searches the knowledge base during live response.
Service Continuity Management​
◎
Run incident response exercises end to end, from scenario design and live sessions to decision logs and retrospectives that feed improvement actions. Track RTO / RPO per service.
Change Enablement​
◎
Pull requests from GitHub become change records, and changes made outside GitHub can be logged manually. Type and risk are classified, unapproved changes are flagged, and recent production changes appear as suspect causes on the incident. Multi-stage CAB approval stays in your ITSM.
Release Management​
◎
A release view lists every change in each release, whether imported from GitHub or entered by hand, so you can answer "what shipped in that release?" from the incident.
Deployment Management​
○
Deployments are recorded per environment with the changes each one delivered. Production rollout times are captured so you can trace their link to outages.
Service Level Management​
○
Set response and resolution SLA targets by priority, measured in business hours. Attainment against SLA, OLA, and UC targets is measured automatically from actual incident data.
Availability Management​
○
Calculate actual availability for any period from incident downtime. Availability targets set as SLOs are evaluated automatically for attainment or breach.
Service Configuration Management​
◎
Built-in CMDB: configuration items and business-continuity layers in one graph, with version history, vector search and site (country/region) records. Blast radius is visualized on the incident, lists scale to thousands of CIs, and data syncs with NetBox and ServiceNow.
Service Catalogue Management​
○
Manage service owners, support hours, and visibility, with links to your existing service request channels.
Supplier Management​
○
Track suppliers by category, criticality, contacts and the services they support, linked to contracts and agreements. A supplier breach impact map shows which services are exposed when a vendor is compromised.
Risk Management​
○
A risk register integrated with problem management, visualized as a 5 × 5 likelihood × impact heat map. Risks are registered automatically from dependency vulnerability (CVE) scans.
Monitoring and Event Management​
Alerts from Datadog, Sentry, Grafana, Rollbar, Zabbix, Instana and Outlook alert mailboxes open incidents automatically, and related alerts are grouped into one.
Measurement and Reporting​
○
An ITIL KPI dashboard covering MTTA / MTTR, SLA compliance, reopen rate, change failure rate, deployment failure rate, change lead time, and more.
Continual Improvement​
○
Raise improvement tasks from incidents, problems, and exercises and track them to completion. Postmortems keep lessons learned within the organization.
Information Security Management​
○
Registers risks from vulnerability (CVE) scans and protects operational data with audit logs, SSO, IP restrictions, and permission groups.
Relationship Management​
○
Stakeholder notifications, status page drafts, and published postmortems keep everyone informed.
Service Request Management​
Request intake integrates with your existing ITSM and portals. The service catalogue points users to your existing request channels.
IT Asset Management​
○
Configuration items, sites, suppliers and contracts live in the built-in CMDB and sync with NetBox and ServiceNow. Financial asset and license management stays in your ITSM.
Service Desk​
Front-line support integrates with your existing service desk. Search and link ServiceNow incident, problem, and change request records, and sync response tasks with them.

Incident Lake is designed to run alongside your ITSM. Keep request intake, multi-stage change approval and license management where they are, and use Incident Lake for configuration context and everything from the first alert to the last follow-up. Ticket sync with Jira, Backlog and ServiceNow is two-way only when an admin enables it.

* ITIL® is a registered trade mark of the PeopleCert group.