Skip to content

Issue

Quick Summary

The primary ticket type for tracking security findings: vulnerabilities, assessment results, scan failures, and ad hoc discoveries. Carries FedRAMP-aligned remediation SLAs and mirrors the Plan of Action and Milestones (POA&M) template for audit-ready record keeping.

The Issue ticket type is the primary vehicle for tracking security findings across the environment. While the scope is broad (issues can originate from penetration tests, configuration compliance scans, assessment findings, or ad hoc discovery), vulnerabilities are the most common source in practice.

Remediation SLAs

Each issue ticket carries a remediation SLA. The applicable model depends on the baseline:

  • FedRAMP Rev5 - the severity ladder:

    Severity Remediation Timeline
    Critical 30 days
    High 30 days
    Moderate 90 days
    Low 180 days
  • FedRAMP 20x - the PAIN-based (Potential Agency Impact N-rating) Class Remediation SLA ladder, with KEV due dates per CISA BOD 26-04 (which survive full mitigation) and a 192-day boundary on accepted vulnerabilities.

See the Vulnerability Detection & Response policy for the full timelines under both models.

Findings from Scanners: Parent and Child Issues

Inbound vulnerability and misconfiguration findings arrive as one post per finding and are filed as a child Issue per asset under one parent Issue per CVE or weakness.

  • Re-posting a finding updates the existing child. A post that changes nothing writes nothing.
  • The parent carries the highest risk of its open children.
  • A remediated post closes the child, and the parent closes with its last child.
  • A child in deviation review keeps its status, and a closed False Positive child is not reopened.

PAIN Events

Each Issue keeps an append-only PAIN Events ledger. A row records each change to the potential agency impact rating, or each evaluation of it.

  • The Initial Evaluation row anchors the remediation window.
  • An Evaluation row records that the Issue was assessed. It never resets the remediation clock and never moves the rating or priority.
  • Every evaluation records a row with a short plain-English note.

Rows cannot be edited after they are written. Only the review flag and review note change.

Automatic Incident Escalation

An open Issue rated at or above the escalation threshold opens an Incident automatically. The Incident opens once the evaluation is recorded, or once the evaluation window passes without one. The window depends on the FedRAMP class:

Class Evaluation window
A 14 days
B 7 days
C 5 days
D 2 days

An Issue opens at most one Incident. If the Issue later drops below the threshold, the automation closes an Incident still in New and records Externally Reportable = No. A daily coverage check confirms that an Issue past its window has a linked Incident.

Exercises

The Is Exercise checkbox marks a ticket as a drill. An exercise Issue is excluded from the Trust Center (Agency) and POA&M reports. It is still scored by validation checks, and its rows carry an EXERCISE: prefix. See FedRAMP Notices.

Issue Details & POA&M Alignment

The fields under the Issue Details tab are purpose-built to mirror the FedRAMP POA&M template, so the ticket record itself becomes the source of truth for continuous monitoring and audit evidence, eliminating double-entry between the ITSM and a separate spreadsheet.

Where possible, issue tickets should be linked to an asset record within the GRC-ITSM platform, though this may not always be applicable depending on the nature of the finding.

Closure

An issue ticket is closed when the finding has been resolved. For vulnerabilities, this means remediation has been confirmed through a rescan or other validated method of verification.