Security incidents such as phishing, malware or data leaks are investigated by the security analyst, contained, and the CISO signs off whether to notify regulators; evidence goes to Drive.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
10
Roles
Security on-call lead, Security analyst, Security manager, CISO, Systems administrator
Apps
Google Drive
Level
Advanced, about 20 min to set up
When something suspicious happens, speed and a clean record matter. Anyone can report a suspected incident. High and critical reports alert the security on-call lead at once. A security analyst investigates and records scope, root cause and actions; the security manager approves the containment, or asks for more investigation. The CISO then approves and signs the decision on external notification (for example to CERT-In within six hours in India, or to customers), the systems administrator completes recovery, and both the evidence and the final report are saved to Google Drive.
Form: Security Incident Report
Starts the workflow
E-mail: request received
Urgent?
If / else
Yes: E-mail: urgent alert · No: Investigate the security incident
E-mail: urgent alert
Investigate the security incident
Task · Security analyst
Mark as done: Approve corrective actions
Approve corrective actions
Approval · Security manager
Approve actions: E-mail: closed · Investigate further: Investigate the security incident
E-mail: closed
Approve & sign external notification decision
Approve & sign · CISO
Notify regulator / customers: Recover systems and rotate credentials · No notification needed: Recover systems and rotate credentials
Recover systems and rotate credentials
Task · Systems administrator
Mark as done: Google Drive: evidence
Google Drive: evidence
App action · Google Drive
Google Drive: incident report
App action · Google Drive
Security Incident Report
Starts the workflow · 10 questions
Incident Investigation
Task form · 4 questions
You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.
Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.
Requests for administrator or privileged accounts are approved and signed by the system owner; the IT administrator then records exactly what was granted and until when, and the record is filed in Drive.
7 steps · 3 rolesEquipment Purchase RequestTeams request new laptops, phones, instruments or tools; the department manager approves and signs, and procurement orders the items and tells the requester the PO and delivery date.
4 steps · 2 rolesHelp Desk Ticket ApprovalHelp desk tickets that need a sign-off are routed by type: purchases to the budget holder, access to the system owner, and every ticket is then approved and signed by the IT support lead.
10 steps · 5 rolesInformation Request ApprovalStaff request a data extract or report; the data owner approves sharing it, a data analyst prepares it with escalation if it stalls, and the data protection officer gets a report.
6 steps · 4 rolesIT Change RequestIT changes are routed by type: standard changes go straight to scheduling, normal changes need the CAB chair's signature and emergency changes the emergency approver's, before the window is booked and implemented.
12 steps · 4 rolesIT Incident ManagementService outages are classified and signed off by the incident manager, resolved by the resolver group, analysed for root cause and formally closed (or reopened) by the service owner.
8 steps · 4 roles