Skip to content

Data Removal Request

Quick Summary

Tracks the removal of unwanted federal customer data when an agency asks for it or a customer spills information into the service. An agent raises the request. The category sets the due date (30 days for an agency removal request, 5 days for a spill), a template adds the removal to-dos, and two daily checks score timeliness and backup scope for KSI-SVC-RUD.

The Data Removal Request ticket type is the record that unwanted data was located, removed, verified and, where appropriate, purged from backups by the date the customer agreement sets. A spill also passes through an incident evaluation, because spilled data can make the event a FedRAMP Reportable Incident.

Do not confuse it with a Data Request, which collects compliance evidence.


Raising a request

An agent raises a Data Removal Request when an agency asks for data to be removed or a spill is found. Fill in the Summary, which is required, and set Date Reported to when the agency made the request or the spill was reported. The due date counts from Date Reported.

Category Due date Use it for
Agency removal request 30 days from Date Reported An agency asks to remove information, for example after a change in how it uses the service
Spill 5 days from Date Reported A customer put information into the service that should not be there

Ticket rules set the priority, and with it the due date, from the category when you create the request in the agent interface.

Requests created through the API

A request created through the API or an AI tool keeps the No agreement window priority until someone sets the priority by hand. That priority records no agreed due date, and both checks Fail a request closed with it. Set the priority to match the category straight away.


Workflow

flowchart LR
    A["New"] -->|"Spill"| B["Incident Evaluation"]
    A -->|"Agency removal request"| C["In Progress"]
    B -->|"Evaluated"| C
    C -->|"Resolve"| D["Closed"]
  1. New. Acknowledge the request.
  2. Incident Evaluation (spills only). Decide whether the spill is an incident. To take Evaluated, either link the Incident you raised or add a note that opens Not an incident (IEC-CSO-EFR): with your reason. Agency removal requests skip this step.
  3. In Progress. Work through the to-dos, then Resolve.

To-dos

Every request gets these to-dos from its template:

To-do Required for the on-time check
Acknowledge Yes
Locate Yes
Remove Yes
Verify Yes
Notify the agency No. No FedRAMP rule requires a notice after removal, so an open one does not fail the check.
Purge backups Complete this one or Backups not in scope, not both
Backups not in scope Complete it with a note opening Backups not in scope (KSI-SVC-RUD): and your reason

Answer No when Resolve offers to close open to-dos

On Resolve, GRC-ITSM asks whether to close the open to-dos. Answer No. Answering Yes completes both backup to-dos, and the backup check Fails a request with both completed.


Validation checks

Two checks score each request when it closes, and a daily sweep scores requests that are past their due date.

Check Pass Fail
On time Closed by the due date with Acknowledge, Locate, Remove and Verify done Past due, closed late, a required to-do missing or open at close, or no agreement window recorded
Backup scope Purge backups completed by the due date, or Backups not in scope completed with its note Neither completed, both completed, Purge backups completed after the due date, Backups not in scope without its note, or no agreement window recorded

A period with no requests writes no rows. The checks measure the process and its timing; they do not prove the data is gone. Exercise requests are scored like real ones, with an EXERCISE: prefix on their rows. See FedRAMP Notices.


Compliance Context

Requirement How this ticket type supports it
Removing Unwanted Data (KSI-SVC-RUD) The on-time and backup scope checks evidence prompt removal, including from backups where appropriate. KSI-SVC-RUD is a 20x indicator: optional on Class B, required on Class C. The consolidated rules publish no Class D statement for it; the organization applies the Class C procedure. It does not apply to Class A or to Rev5.
Evaluate FedRAMP Reportability (IEC-CSO-EFR, MUST) A spill cannot leave Incident Evaluation without a linked Incident or a written reason it is not one

See the Data Removal policy for the policy and procedure, and Incident for how a spill that is an incident is evaluated and reported.