On 7/6/12 2:59 PM, Willy Santos wrote:
CCI-000553 requires implementing transaction recovery for transaction-based
systems. This mapping is a request for input/discussion.
Signed-off-by: Willy Santos <[email protected]>
---
rhel6/src/input/auxiliary/srg_support.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/rhel6/src/input/auxiliary/srg_support.xml
b/rhel6/src/input/auxiliary/srg_support.xml
index 70a6c15..80d690f 100644
--- a/rhel6/src/input/auxiliary/srg_support.xml
+++ b/rhel6/src/input/auxiliary/srg_support.xml
@@ -38,7 +38,7 @@ The requirement is impractical or out of scope.
<description>
It is unclear how to satisfy this requirement.
</description>
-<ref disa="20,31,218,219,224,1097,1158,1291,1294,1295,1395,1428,1500" />
+<ref disa="20,31,218,219,224,1097,1158,1291,1294,1295,1395,1428,1500,553" />
</Group> <!-- end requirement_unclear -->
<Group id="new_rule_needed">
SRG-OS-000102 CCI-000553 The operating system must implement
transaction recovery for transaction-based systems. Recovery and
reconstitution constitutes executing an operating system contingency
plan comprised of activities to restore essential missions and business
functions. Transaction rollback and transaction journaling are examples
of mechanisms supporting transaction recovery. While this is typically a
database function, operating systems could be transactional in nature
with respect to file processing.
The OS may provide enabling technologies like journaling, but the OS
itself isn't responsible for the transaction. That's the middlewares job.
impractical_product.
_______________________________________________
scap-security-guide mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/scap-security-guide
