Skip to content

Data Removal

This document establishes the organization's policy for removing unwanted federal customer data from the system when an agency asks for it, and the procedures by which GRC-ITSM executes that policy. It covers the two cases the indicator names: an agency asking to remove information because its use of the service has changed, and a customer spill. It describes the Data Removal Request ticket, its removal windows, the incident evaluation every spill receives, the removal steps carried as to-dos, the backup decision, and the daily checks that evidence the process. It implements the FedRAMP 20x Key Security Indicator for removing unwanted data (KSI-SVC-RUD) and applies the incident reportability rule (IEC-CSO-EFR) to spills.

Quick Summary

An agent raises a Data Removal Request for each agency request to remove data and each customer spill. The category sets the window: 30 days for an agency removal request and 5 days for a spill, counted from the Date Reported. Every spill passes an incident evaluation before removal starts, and every request works the same to-dos, including a recorded backup decision. Two daily checks score each request for timeliness and backup scope against KSI-SVC-RUD, which is required at FedRAMP 20x Class C and optional at Class B.

Related documentation

Related documents own the adjacent disciplines. A spill that is an incident is handled under the Incident Response Policy and Procedures. The validation structure the evidence lands in is described in the Continuous Monitoring and Reporting Policy and Procedures.

Download the KB article (Markdown)


Framework applicability

Framework What this document satisfies
FedRAMP 20x (Class C) KSI-SVC-RUD, Removing Unwanted Data: "Unwanted federal customer data is removed promptly when requested by an agency in alignment with customer agreements, including from backups if appropriate; this typically applies when a customer spills information or when a customer seeks to remove information from a service due to a change in usage." IEC-CSO-EFR for the evaluation of each spill
FedRAMP 20x (Class B) KSI-SVC-RUD is optional at Class B; the procedure runs the same way when adopted
FedRAMP Rev5 IEC-CSO-EFR for the evaluation of each spill. KSI-SVC-RUD is a 20x indicator and has no Rev5 class

KSI-SVC-RUD is required at 20x Class C and optional at Class B. The consolidated rules publish no Class D statement for this indicator; the organization applies the Class C procedure. The indicator says "promptly" and sets no number of days; the Organization-defined values table carries the windows this procedure applies.


Policy

  • P-1. Every removal is a Data Removal Request. An agent raises a Data Removal Request ticket for each agency request to remove data and for each customer spill. The ticket is the record of the request, the work, and the outcome.
  • P-2. The category sets the window. The ticket's category is Agency removal request or Spill. The category selects the agreement window: 30 days for an agency removal request and 5 days for a spill. The due date counts from the Date Reported on the ticket.
  • P-3. Every spill is evaluated for reportability. A spill may affect the confidentiality or integrity of federal customer data, so every spill passes an Incident Evaluation step before removal starts (IEC-CSO-EFR, MUST). The step closes only with a linked Incident or a note that records why the spill is not an incident.
  • P-4. Removal follows fixed steps. Each request carries the same to-dos: acknowledge the request, locate the data, remove it, verify the removal, notify the agency, and record the backup decision. A request missing one of these to-dos fails the on-time check.
  • P-5. Backups are decided, not assumed. Each request records one backup outcome: the backups were purged, or backups are not in scope for this data. The agent completes the to-do that applies and leaves the other open.
  • P-6. The agency hears back. The agent notifies the requesting agency when removal is complete. No FedRAMP rule requires this notice, so its absence does not fail the on-time check; the organization keeps it as practice.
  • P-7. Evidence is written by the process. Daily checks score each request for timeliness and for its backup decision, without anyone assembling evidence.
  • P-8. The procedure reviews itself. The ISSO reviews this document for effectiveness on the cadence in the Organization-defined values table.

Organization-defined values

Value Setting Default Force
Agency removal request window [days] 30 days from Date Reported, counted around the clock Required at 20x Class C (KSI-SVC-RUD: "promptly")
Spill removal window [days] 5 days from Date Reported, counted around the clock Required at 20x Class C (KSI-SVC-RUD: "promptly")
Due date anchor Date Reported The Date Reported field on the ticket N/A
Spill reportability evaluation Linked Incident, or a note opening "Not an incident (IEC-CSO-EFR):" Required before removal starts on every spill MUST (IEC-CSO-EFR)
Backup handling Purge backups, or record Backups not in scope One of the two, recorded as a to-do Required at 20x Class C (KSI-SVC-RUD: "including from backups if appropriate")
Agency notification after removal Notify the agency to-do Sent on every request N/A (no FedRAMP rule requires it)
Validation schedule On each status change, and daily at 06:00 UTC Same N/A
Data removal procedure effectiveness review [cadence] At least annually N/A

Roles and responsibilities

  • Requesting agency. Asks for the removal, or reports the spill, and receives the completion notice.
  • Assigned agent. Raises the Data Removal Request, acknowledges it, works the to-dos, records the backup decision, and resolves the ticket.
  • Evaluating responder. For a spill, decides whether the spill is an incident: links the Incident it opened, or records why it is not one.
  • System and data administrators. Locate and remove the data, and purge backups where backups are in scope.
  • ISSO and System Owner. Accountability and escalation. The ISSO reviews this document on the cadence in the Organization-defined values table; the System Owner gives final approval and authorizes exceptions.

The Data Removal Request

An agent raises a Data Removal Request with a category, a summary, and the Date Reported. The category is the only branch in the workflow.

Category Window Workflow
Agency removal request 30 days New, then In Progress, then Closed
Spill 5 days New, then Incident Evaluation, then In Progress, then Closed
flowchart TD
    A["Request raised with category,<br/>summary, and Date Reported"] --> B["New: Acknowledge"]
    B --> C{"Category"}
    C -->|Agency removal request| E["In Progress:<br/>locate, remove, verify, backups, notify"]
    C -->|Spill| D["Incident Evaluation:<br/>linked Incident, or a<br/>'Not an incident' note"]
    D --> E
    E --> F["Resolve: Closed"]

Every request carries KSI-SVC-RUD automatically, attributed by its category. The request can be marked as an exercise with the Is Exercise checkbox; the FedRAMP Notices user guide describes how exercise tickets are handled.

The agreement window

The window is the ticket's priority. A ticket rule sets it from the category when an agent creates the request in the agent interface: Agency removal request - 30 days, or Spill - 5 days. The window runs around the clock, so the due date is the Date Reported plus 30 or 5 calendar days.

Requests created through the API

The ticket rule fires when a request is created in the agent interface. A request created through the API keeps the default priority, No agreement window, until an agent sets its priority. Set the priority before working the request, or it has no due date.

Spill incident evaluation

A spill moves to Incident Evaluation after it is acknowledged. The evaluating responder decides whether the spill affects, or is likely to affect, the confidentiality or integrity of federal customer data (IEC-CSO-EFR, MUST), and records the outcome with the Evaluated action:

  • The spill is an incident. The responder opens an Incident and links it to the request. The Incident then follows the Incident Response Policy and Procedures, and its own reportability evaluation and notices are scored there.
  • The spill is not an incident. The responder records a note that opens "Not an incident (IEC-CSO-EFR):" followed by the reason.

The step does not close without one of the two. An agency removal request skips this step.

The removal to-dos

Every request carries the same to-dos from its template.

To-do What it records
Acknowledge The request is received and owned
Locate Where the data lives, including copies
Remove The data is removed
Verify The removal is confirmed
Notify the agency The requesting agency is told the removal is complete
Purge backups Backups holding the data are purged
Backups not in scope Backups do not hold this data, or are outside what the request covers

Complete the backup to-do that applies and leave the other open.

Answer No to closing open to-dos

When you resolve the request, the platform asks whether to close the open to-dos. Answer No. Answering Yes completes both backup to-dos, and a request with both completed fails the backup-scope check.


Automated validation evidence

Operating this process produces machine validation evidence automatically. The data removal validation runs on every status change of a Data Removal Request and daily at 06:00 UTC, and writes dated rows against KSI-SVC-RUD on two checks.

Check What it scores
On time Whether the request was completed within its agreement window. A request missing one of the template to-dos fails. An open Notify the agency to-do does not fail it
Backup scope Whether the request recorded one backup outcome. A request with both Purge backups and Backups not in scope completed fails

A period with no Data Removal Requests writes no rows. The checks evidence the process: that each request was handled on time and that its backup decision was recorded. They do not inspect the system to confirm that the data is gone; the Verify to-do records that confirmation.

A spill's reportability evaluation is not scored here. When a spill is an incident, the linked Incident's evaluation is scored by the incident checks under the Incident Response Policy and Procedures.


Authority, review, and revision

Issued under the authority of the System Owner and binding on all personnel with access to the system. Exceptions require written System Owner approval and are documented.

The ISSO reviews this document for effectiveness on the cadence in the Organization-defined values table, and when frameworks, the system, or lessons learned warrant; the System Owner gives final approval. The annual plan and policy review task under the Annual cadence parent is where that review is tracked.


Document What it owns
Incident Response Policy and Procedures A spill that is an incident: its evaluation, reporting, and After Action Report
Continuous Monitoring and Reporting Policy and Procedures The validation structure the data removal evidence lands in
Data Removal Request ticket type user guide The fields, actions, and to-dos on the ticket
FedRAMP Notices user guide Exercise handling and the notice windows for a spill that becomes a reportable incident

FedRAMP coverage

KSI-SVC-RUD, Removing Unwanted Data (20x only; required at Class C, optional at Class B): the Data Removal Request, its windows, the backup decision, and the two daily checks are the claim. IEC-CSO-EFR, Evaluate FedRAMP Reportability (MUST): every spill is evaluated before removal starts. No FedRAMP rule requires notifying the agency after removal; the organization does it as practice.