-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
M-21-31: Identify gaps in event logging requirements #1555
Labels
g: accepted
Issue has been fully groomed.
m: due date
Has a hard or soft deadline
t: weeks
Should be complete-able in a matter of weeks (wall clock time) — see what can be split out
Comments
rocheller123
added
the
g: initial
Issue template needs to be filled out, and/or initiative/timing labels need to be added.
label
Sep 1, 2021
rocheller123
changed the title
M-21-31: Identify gaps in event logging requirements as per memo
M-21-31: Identify gaps in event logging requirements - Due 10/26/2021
Sep 2, 2021
afeld
added
the
t: weeks
Should be complete-able in a matter of weeks (wall clock time) — see what can be split out
label
Sep 8, 2021
afeld
moved this from New
to Backlog (Sprint Staging)
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Sep 8, 2021
afeld
moved this from Backlog (Sprint Staging)
to Ready (Sprint Planned)
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Sep 20, 2021
adborden
moved this from Ready (Sprint Planned)
to In Progress
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Sep 23, 2021
adborden
added
g: accepted
Issue has been fully groomed.
and removed
g: initial
Issue template needs to be filled out, and/or initiative/timing labels need to be added.
labels
Sep 27, 2021
rocheller123
moved this from In Progress
to Waiting/Feedback
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Oct 4, 2021
Discussed in Slack: https://gsa-tts.slack.com/archives/CG8SNAEQM/p1636040839007600 |
JJediny
changed the title
M-21-31: Identify gaps in event logging requirements - Due 10/26/2021
M-21-31: Identify gaps in event logging requirements
Apr 4, 2022
JJediny
moved this from Waiting/Feedback
to Ready (Sprint Planned)
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Apr 4, 2022
JJediny
removed this from Ready (Sprint Planned)
in TTS Technology Portfolio (DEPRECATED/ARCHIVE)
Jan 22, 2024
JJediny
assigned MichaelSides and unassigned josephderosales, rpalmer-gsa and rocheller123
May 2, 2024
Week of June 3rd:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
g: accepted
Issue has been fully groomed.
m: due date
Has a hard or soft deadline
t: weeks
Should be complete-able in a matter of weeks (wall clock time) — see what can be split out
Background Information
M-21-31: Improving the Federal Government’s Investigative and Remediation Capabilities Related to Cybersecurity Incidents requires federal agencies to log information to aid in the "detection, investigation, and remediation of cyber threats" and to share information with other agencies, if required, to address cybersecurity risks or incidents.
The required log information is broken down into 4 Event Logging (EL) tiers: EL0, EL1, EL2, EL3.
The requirements for ensuring the information for each tier is being collected are as follows with specific deadlines from date of memo (8/27/2021):
The first step is to identify the required information that is not being collected and to create a plan to ensure the information is being collected.
Implementation Steps
Acceptance Criteria
The text was updated successfully, but these errors were encountered: