Help:Contents: Difference between revisions

From HORSE - Holistic Operational Readiness Security Evaluation.
Jump to navigation Jump to search
No edit summary
Line 32: Line 32:
----
----
[[Text formatting help]].<br>
[[Text formatting help]].<br>
[[Table formatting help]].
[[Table formatting help]].<br>
[http://diberri.dyndns.org/wikipedia/html2wiki/index.html HTML to Wiki conversion.}
----
----
<br>
<br>

Revision as of 10:53, 2 April 2007

File:Greenlock.jpg The status of this control objective is acceptable.

File:Yellowlock.jpg The status of this control objective requires additional attention.

File:Bluelock.jpg The status of this control objective has been remediated.

File:Redlock.jpg The status of this control objective is not acceptable and requires remediation.



The risk potential condition is low. Use this image to provide a visual indication.

The risk potential condition is medium. Use this image to provide a visual indication.

The risk potential condition is high. Use this image to provide a visual indication.



Use this icon to visually illustrate what would be considered a key control.



Consult the User's Guide for information on using the wiki software.

Getting started



Text formatting help.
Table formatting help.
[http://diberri.dyndns.org/wikipedia/html2wiki/index.html HTML to Wiki conversion.}



A brief explanation of industry or legislative control requirments can be found through the links below.

COBIT
Sarbanes-Oxley
HIPAA
GLBA
PCI
FISMA
NIST SP 800-66
Ditscap
DOI
Control Exception: If a control condition exists that is exempt from testing, documentation should be available.
User Defined: Any control that is truly unique to the enterprise should be noted accordingly.


--Mdpeters 10:46, 10 May 2006 (EDT)