The Federal IT Papers–Part 6

Evolution of Security

A CSAM that is used for all agencies is a key component for the continued evolution of agency cyber capabilities. As we already know, agencies are deploying sensors that help to understand vulnerabilities. Those vulnerabilities are lighting up dashboards like Christmas trees. We need to home in on the finite list of vulnerabilities. As such, anything that helps us to subtract lights from the dashboard is a good thing. All that POA&M data is in CSAM. Thus if we can make a link between the POA&M and a vulnerability that we are already working, then there is a segment of the noise that we can wipe away.

In order for this to have merit we need to get serious about managing POA&Ms. Their max duration must have rules and there must be a limit about how many times you can re-up them. I have seen agencies create a POA&M for six months and even year-long durations. That is completely unacceptable. If a POA&M lasts more than a month (for a critical or high), without something to mitigate the issue then you might as well quit now.

Agencies have also gamed the system by extending POA&Ms. They will create a POA&M and give it a due date of two weeks but then every two weeks they extend it for another two weeks until you get six months or a year down the line and you realize that you have been played like a banjo on the knee of a hick missing three teeth. The other big way agencies game POA&Ms is by closing down a POA&M and opening a new one on the same issue for the same system.

To address these problems agencies need to be held accountable for:

  • Completely reporting their POA&Ms.
  • How many POA&Ms they are carrying on a daily basis.
  • The average duration of their POA&Ms.
  • Percentage of POA&Ms that are extended.

This set of data will help oversight organizations to understand the level of risk different organizations are willing to accept.

 

In This Series:

The Federal IT Papers–Part 1

The Federal IT Papers–Part 2

The Federal IT Papers–Part 3

The Federal IT Papers–Part 4

The Federal IT Papers–Part 5

The Federal IT Papers–Part 6

The Federal IT Papers–Part 7

The Federal IT Papers–Part 8

The Federal IT Papers–Part 9

The Federal IT Papers–Part 10

The Federal IT Papers–Part 11

The Federal IT Papers–Part 12

1   http://www.gsa.gov/portal/content/215823

2   http://www.splunk.com/goto/SIEM_MQ

3   http://www.wired.com/2016/01/the-biggest-security-threats-well-face-in-2016/

4   https://www.congress.gov/bill/108th-congress/house-bill/2622?q=%7B%22search%22%3A%5B%22%5C%22hr2622%5C%22%22%5D%7D&resultIndex=1

5 http://www.computerworld.com/article/2563635/security0/sidebar–the-mosaic-effect.html

6 <sup>6</sup>  http://www.darkreading.com/cloud/cybercrime-a-black-market-price-list-from-the-dark-web/d/d-id/1324895?

7   http://www.mcafee.com/us/resources/reports/rp-hidden-data-economy.pdf

8  https://www.performance.gov/downloadpdf?file=Sprint%20Results%20Report%20FY15_Q2.pdf

9  https://www.performance.gov/downloadpdf?file=FY15%20Q3%20Cybersecurity%20FINAL_4.pdf

10   https://www.performance.gov/downloadpdf?file=FY15%20Q3%20Cybersecurity%20FINAL_4.pdf

11   http://www.cbsnews.com/news/gsa-system-showed-ssns-for-183k-contractors/

 

 

 

Demosthenes
About Demosthenes
Demosthenes is a pseudonym for a senior Federal IT official.

Categories

Recent