08.11.2012 Views

Evaluation of Department of State Information Security Program ...

Evaluation of Department of State Information Security Program ...

Evaluation of Department of State Information Security Program ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

UNCLASSIFIED<br />

9<br />

• Develop operating procedures to ensure the results are included in the Risk Scoring<br />

<strong>Program</strong> dashboard.<br />

• Develop procedures to ensure that System <strong>Security</strong> Owners update the system security<br />

plans to include a continuous monitoring strategy to detail how system security controls<br />

are to be monitored.<br />

<strong>Department</strong> Response to Recommendation 11:<br />

Regarding bullet 1, the <strong>Department</strong> notes that implementation <strong>of</strong> an effective continuous<br />

monitoring strategy will require continuous improvement and thus never be completed.<br />

The <strong>Department</strong>'s current continuous monitoring implementation is being copied as a<br />

model by both other government agencies and the private sector.<br />

Regarding bullet 2, the <strong>Department</strong> is already engaged in these efforts and will pursue<br />

them with an appropriate level <strong>of</strong> priority. Test scans <strong>of</strong> routers and switches show that if<br />

the height <strong>of</strong> the Washington Monument represented the total risk in place in the summer<br />

<strong>of</strong>2008, the risk <strong>of</strong> "uncovered" routers and switches would be less than 0.34 inches<br />

high. The <strong>Department</strong> will continue to prioritize such risks and expand the coverage <strong>of</strong><br />

the risk scoring program.<br />

Regarding bullet 3, the <strong>Department</strong> will continue to expand coverage <strong>of</strong> risk in iPost in<br />

line with the priorities established under bullet 2.<br />

Regarding bullet 4, the <strong>Department</strong> notes that the continuous monitoring strategy is an<br />

enterprise level strategy. Thus, the continuous monitoring strategy does not need to be<br />

addressed in detail in every system security plan.<br />

Recommendation 12: {Section H} We recommend that the Chief <strong>Information</strong> Officer, in<br />

accordance with NIST SP 800-34, Revision 1, "Contingency Planning Guide for Federal<br />

<strong>Information</strong> Systems" take the following actions:<br />

• Update the Continuity <strong>of</strong> Operations Communication Plan annually or when changes<br />

occur to the organization, network hardware, systems, and applications and, if necessary,<br />

after Continuity Testing.<br />

• Perform an entity-wide Business Impact Analysis and develop a strategy to prioritize<br />

recovery <strong>of</strong> the critical assets within the <strong>Department</strong> <strong>of</strong> <strong>State</strong>.<br />

• Update the section <strong>of</strong> the Foreign Affairs Manual that contains guidance and direction for<br />

development and implementation <strong>of</strong> Continuity <strong>of</strong> Operations Communication Plan.<br />

<strong>Department</strong> Response to Recommendation 12:<br />

The <strong>Department</strong> will:<br />

UNCLASSIFIED<br />

70<br />

UNCLASSIFIED

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!