One incident record
Bring evidence, timeline, comments, communications, and reports together.
GRC login ↗Report, investigate, notify, and close security incidents in a single application, with built-in playbooks, SLA timers, evidence tracking, and AI that helps you write. People make the decisions.
Bring evidence, timeline, comments, communications, and reports together.
Assign responsibility and monitor deadlines so work and overdue items stay visible.
Capture decisions and evidence as you work, rather than rebuilding them when the report is due.
Use a guided form or the emergency Under Attack? action. Likelihood and impact inform risk and suggested priority.
Assign an owner, follow status and SLA timers, and record the timeline and communications.
Use a playbook with a Next Action, tool, log source, checklist, and evidence links.
Obtain required closure approval, publish the reviewed report, and capture lessons learned.
Suggested playbooks are applied by the analyst. Next Action guidance explains which configured tool and log to use, and why.
Record hashes, storage locations, and hand-offs. Uploaded evidence is stored privately.
Track open incidents on a response board, assign owners, mention teammates, and monitor response and escalation timers.
Log notifications, send messages to saved contacts, and track regulatory notification due dates. Tracking an obligation does not establish compliance.
Review an incident overview, timeline, indicators, and notifications alongside findings and recommendations. Publish Word, PDF, or text reports.
Maintain playbooks, log lessons learned, and track tabletop exercises, drills, training, and remediation.
AI rewrites rough notes and drafts executive summaries, findings, and recommendations. People review, save, and publish.
AI describes screenshots and summarizes logs and documents for analyst review, separately from the formal evidence record.
Ask questions using the incident’s data. The Copilot cannot change records, close incidents, or act on your systems.
Open incidents automatically using a Falcon Fusion workflow that calls the REST API. This connection is verified working in the supplied product brief.
API keys authorize incident creation and listing. Updating or closing incidents through the API is not available.
Signed webhooks notify your systems when an incident is created, changes status, is assigned, or escalates. Chat delivery requires an automation tool.
Viewers read incidents and reports. Users can also raise incidents, comment, and record timeline entries and indicators.
Managers handle response work and publish reports. Admins also manage team access and settings. Serious closures require a separate approver.
MSSP Analysts perform response work. MSSP Managers can approve closures and publish; MSSP Admins also manage provider administration.
Authenticator-app MFA, recovery codes, lockout controls, and Microsoft sign-in where configured.
Organization data is isolated. Provider staff see only clients they have been granted.
High and Extreme closures need an Admin or Manager other than the assignee. API keys are hashed, scoped, rate-limited, and revocable; webhooks are signed.
Review open and critical incidents, SLA status, resolution time, volume, and response cost.
Maintain declarations, daily reports, notification logs, and regulatory deadline tracking.
Review granted clients from one login, switch into the active tenant, and manage staff access per client.
It coordinates the response. Your security tools detect; uSAFE records, assigns, and reports.
No. AI drafts and summarizes for review. The Copilot is read-only and cannot act on systems.
Yes. Closing a High or Extreme incident requires an Admin or Manager other than the person assigned.
Final reports can be published as Word, PDF, or text, with additional declarations, daily reports, and data exports.
Tell us about your priorities and the workflows you want to explore.
uSAFE Callback Request