For: Companies Private IT Partner v1.0.816 · Swiss Made
For: v1.0.816 · Swiss Made

Incidents & tickets

The central place to record, handle and close security incidents.

Ticket hub for incidents: status (open, in progress, closed), priority, category and damage type, assignment, message thread with edit history, links to war room and MITRE techniques.

← All modules
A LOOK INSIDE
Incidents & tickets · Overview Incidents & tickets · Overview
Overview Sample data
Incidents & tickets · Detail view Incidents & tickets · Detail view
Detail view Sample data
Incidents & tickets · Investigation Incidents & tickets · Investigation
Investigation Sample data

All reported security incidents of your company come together here as tickets — from a suspicious email to a lost laptop to an active attack. Each ticket has a status, an urgency and a responsible person. No report gets lost, and everyone can see what is open and who is taking care of it.

The incident hub bundles all security incidents as tickets with a full lifecycle: intake, categorisation, prioritisation, assignment and closure. Each ticket keeps a history for traceable documentation. You escalate severe incidents directly to the war room for coordinated handling.

Features
  • All incident reports of the company in one central place.
  • Each ticket with status, urgency, responsible person and history.
  • Filters by status, urgency or search term for a quick overview.
  • Serious incidents can be handed over to a crisis room (war room).
  • The entire history stays documented and traceable.
  • Central ticket lifecycle from intake to closure.
  • Categorisation, prioritisation and assignment per incident.
  • Filters by status, priority and search term across all tickets.
  • Escalation of severe incidents to the war room.
  • Complete history as an audit trail.
  • Intake of reports from employee submissions and security modules.
How it works
  1. You record a new incident, or a report comes in from an employee.
  2. You set urgency and status and assign the ticket to a person.
  3. You filter the list to keep track of open and urgent tickets.
  4. For a serious incident, you hand the ticket over to the crisis room.
  1. You record incidents manually, or they arrive from employee reports and modules.
  2. You triage: set category, priority and responsible person.
  3. You work the ticket and document steps in the history.
  4. You escalate severe cases to the war room.
  5. You close the ticket; the history is retained for audits.

Use it forManage incidents in an orderly, traceable way.

Use it forHandle and document incidents in a structured way.

In the ICT minimum standard
PR · Protect
  • PR.IP-7Ensure that your information security procedures are enhanced and improved continuously.
  • PR.IP-9Establish response procedures for any cyber incidents that may occur. (Incident response planning, business continuity management, incident recovery, disaster recovery.)
DE · Detect
  • DE.AE-2Ensure that detected cybersecurity incidents are analysed to understand their targets and methods.
  • DE.AE-3Ensure that information on cybersecurity incidents is aggregated and correlated from multiple sources and sensors.
  • DE.AE-4Determine the impact of possible events.
  • DE.AE-5Define the thresholds above which cybersecurity incidents trigger an alert.
  • DE.DP-4Communicate detected incidents to the relevant actors (e.g. suppliers, customers, partners, authorities, etc.).
  • DE.DP-5Improve your detection processes continuously.
RS · Respond
  • RS.AN-1Ensure that notifications from detection systems are noted and investigated.
  • RS.AN-2Ensure that the impact of a cybersecurity incident is properly understood.
  • RS.AN-4Categorise incidents that occur in accordance with the requirements of the response plan.
  • RS.CO-1Ensure that all individuals are familiar with their response and the sequence of their actions if and when a cybersecurity incident occurs.
  • RS.CO-2Define reporting criteria and ensure that cybersecurity incidents are reported and processed in accordance with these criteria.
  • RS.CO-3Share information and findings about detected cybersecurity incidents in accordance with the defined criteria.
  • RS.CO-4Coordination with stakeholders occurs consistent with response plans
  • RS.IM-1Ensure that the findings and lessons of previous cybersecurity incidents are incorporated into your response plans.
  • RS.IM-2Update your response strategies.
  • RS.MI-1Ensure that cybersecurity incidents can be contained and their further spread blocked.
  • RS.MI-2Ensure that the impact of cybersecurity incidents can be mitigated.
  • RS.RP-1Ensure that the response plan is executed promptly and properly during or after a detected incident.
RC · Recover
  • RC.CO-1Ensure that public perceptions of your organisation are addressed actively.
  • RC.CO-2Ensure that your organisation is perceived positively once again after any cybersecurity incident.
  • RC.CO-3Communicate all of your recovery activities to internal stakeholder groups, and especially also to (senior) management.
  • RC.IM-1Ensure that the findings and lessons of previous cybersecurity incidents are incorporated into your recovery plans.