---
src/share/transforms/about.html | 39 ++++++++++++++++++++++
src/share/transforms/help.html | 68 +++++++++++++++++++++++++++++++++++++++
2 files changed, 107 insertions(+), 0 deletions(-)
create mode 100644 src/share/transforms/about.html
create mode 100644 src/share/transforms/help.html
diff --git a/src/share/transforms/about.html b/src/share/transforms/about.html
new file mode 100644
index 0000000..775ec13
--- /dev/null
+++ b/src/share/transforms/about.html
@@ -0,0 +1,39 @@
+<!DOCTYPE html PUBLIC "--//W3C//DTD XHTML 1.0 Strict//EN"
"DTD/xhtml1-strict.dtd">
+<html>
+ <head>
+ <title>SecState Audit Results</title>
+ <link id="style" rel="stylesheet"
href="media/css/main.css" type="text/css" media="screen"
/>
+ <link rel="stylesheet" href="media/css/print.css"
type="text/css" media="print" />
+ <script type="text/javascript"
src="media/js/jquery-1.4.2.min.js"></script>
+ <script type="text/javascript"
src="media/js/custom.js"></script>
+ </head>
+ <body>
+ <div id="wrap">
+ <div id="header">
+ <span id="secstate">
+ <h1>SecState</h1> Version 1.0<br/>
+ System Security Compliance & Audit Tool
+ </span>
+ <span id="nav">
+ <a id="print" href="#">Print</a>
+ </span>
+ </div>
+ <div id="about">
+ <dl>
+ <dt>About SecState</dt>
+ <dd>SecState is a tool that attempts to streamline the
Certification and Accreditation (C&A) process of Linux systems. SecState provides
a mechanism to verify, validate, and provide remediation to security relevant
configuration items. The projects main goals are to provide a user friendly interface to
configure the security state of a system and generate evidence that it is configured as
such, to be usede within the C&A process.</dd>
+ <dt>FAQ</dt>
+ <dd>
+ <dl id="faq">
+ <dt>Q: Sample Question</dt>
+ <dd>A: Sample Answer</dd>
+ </dl>
+ </dd>
+ <dt>About Tresys</dt>
+ <dd> description</dd>
+ </dl>
+ </div>
+ </div>
+ <div id="footer"><span id="tresys">Tresys
Technology, LLC</span><span id="version">Version
1.0</span></div>
+ </body>
+</html>
diff --git a/src/share/transforms/help.html b/src/share/transforms/help.html
new file mode 100644
index 0000000..702618a
--- /dev/null
+++ b/src/share/transforms/help.html
@@ -0,0 +1,68 @@
+<!DOCTYPE html PUBLIC "--//W3C//DTD XHTML 1.0 Strict//EN"
"DTD/xhtml1-strict.dtd">
+<html>
+ <head>
+ <title>SecState Audit Results</title>
+ <link id="style" rel="stylesheet"
href="media/css/main.css" type="text/css" media="screen"
/>
+ <link rel="stylesheet" href="media/css/print.css"
type="text/css" media="print" />
+ <script type="text/javascript"
src="media/js/jquery-1.4.2.min.js"></script>
+ <script type="text/javascript"
src="media/js/custom.js"></script>
+ </head>
+ <body>
+ <div id="wrap">
+ <div id="header">
+ <span id="secstate">
+ <h1>SecState</h1> Version 1.0<br/>
+ System Security Compliance & Audit Tool
+ </span>
+ <span id="nav">
+ <a id="print" href="#">Print</a>
+ </span>
+ </div>
+ <div>
+ <dl id="help">
+ <dt class="title">Benchmark Result
Definitions:</dt>
+ <dd>
+ <dl class="help">
+ <dt>Pass:</dt>
+ <dd>The target system or system component satisfied all the
conditions of the Rule; a pass result contributes to the weighted score and maximum
possible score.</dd>
+ <dt>Fail:</dt>
+ <dd>The target system or system component did not satisfy
all the conditions of the Rule; a fail result contributes to the maximum possible
score.</dd>
+ <dt>Error:</dt>
+ <dd>The checking engine encountered a system error and
could not complete the test, therefore the status of the target's compliance with the
Rule is not certain. This could happen, for example, if a Benchmark testing tool were
runwith insufficient privileges.</dd>
+ <dt>Unknown:</dt>
+ <dd>THe testing tool encountered some problem and the
result is unknown. For example, a result of 'unknown' might be given if the
Benchmark testing tool were unable to interpret the output of the checking
engine.</dd>
+ <dt>Not Applicable</dt>
+ <dd>The Rule was not applicable to the target of the test.
For example, the Rule might have been specific to a different version of the target OS, or
it might hvae been a test against a platform feature that was not installed. Results with
this status do not contribute to the Benchmark score.</dd>
+ <dt>Not Checked</dt>
+ <dd>The Rule was not evaluated by the checking engine.
This status is designed for Rules witha role of 'unchecked', and for Rules that
have no check properties. It may also correspond to a status returned by a checking
engine. Results with this status do not contribute to the Benchmark score.</dd>
+ <dt>Not Selected</dt>
+ <dd>The Rule was not selected in the Benchmark. Results
with this status do not contribute to the Benchmark score.</dd>
+ <dt>Informational/Mitigated</dt>
+ <dd>The Rule was checked, but the output from the checking
engine is simply information for the auditor or administrator; it is not a compliance
category. This status is the default for Rules with a role of 'unscored'. This
status value is designed for Rules whose main purpose is to extract information from the
target rather than test compliance. Results with this status do not contribute to the
Benchmark score.</dd>
+ <dt>Fixed</dt>
+ <dd>The Rule had failed, but was then fixed (possibly by
SecState or by the human auditor). Results with this status should be scored the same as
<b>Pass</b>.</dd>
+ </dl>
+ </dd>
+ <dt class="title">OVAL Result Definitions:</dt>
+ <dd>
+ <dl class="help">
+ <dt>Pass:</dt>
+ <dd>When evaluating a definition or test, the
characteristics being evaluated matched the information represented in the system
characteristic file.</dd>
+ <dt>Fail:</dt>
+ <dd>When evaluating a definition or test, the
characteristics being evaluated did not match the informatoin represented in the system
characteristic file.</dd>
+ <dt>Unknown:</dt>
+ <dd>When evaluating a definition or test, the
characteristics being evalutaed could not be found in the system characteristic file or
the characteristics can be found but a collected object's flag is 'not
collected'.</dd>
+ <dt>Error:</dt>
+ <dd>When evaluating a definition or test, the
characteristics being evaluted exist in the system characteristic file but there was an
error either collecting information or in performing analysis. For example, if there was
an error returned by an api when trying to determine if an object exists on a
system.</dd>
+ <dt>Not Evaluated:</dt>
+ <dd>When evaluating a definition or test, a choice was made
not to evaluate the given definition or test. The actual result is in essence unknown
since if evaluation had occurred it could have been either true or false.</dd>
+ <dt>Not Applicable:</dt>
+ <dd>When evaluating a definition or test, the definition or
test being evaluated is not valid on the given platform. For example, trying to collect
Linux RPM information on a Windows system.</dd>
+ </dl>
+ </dd>
+ </dl>
+ </div>
+ </div>
+ <div id="footer"><span id="tresys">Tresys
Technology, LLC</span><span id="version">Version
1.0</span></div>
+ </body>
+</html>
--
1.7.2.2
Show replies by date