Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update security-incidents.md #4081

Merged
merged 3 commits into from
Feb 6, 2025
+2 −2
Merged

Update security-incidents.md #4081

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a22f0b9
Update security-incidents.md
narumigsa Jan 17, 2025
e7ecf9d
Update security-incidents.md
JJediny Feb 6, 2025
5036272
Merge branch 'main' into patch-10
JJediny Feb 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/general-information-and-resources/tech-policies/security-incidents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
title: Security incidents
redirect_from:
- /security-incidents/
cSpell: ignore Cofense
cSpell: ignore Cofense, TTS's
---

Something went "bump" in the night (or the day)? This document explains what to
Expand Down Expand Up @@ -107,7 +107,7 @@ steps.
## What is an incident?

First: it's always OK to err on the side of reporting!
[TTS](https://www.gsa.gov/portal/category/25729)'s and GSA's incident response
TTS's and GSA's incident response
teams are good at their job, and they are totally used to false alarms. You'll
never get in trouble for pinging them about something that turns out not to be
an issue! Indeed, _you'll never get in trouble for pinging IR at all_. The most
Expand Down