[Zope3-checkins] CVS: Zope3/doc/security - SecurityTarget.txt:1.13

[Christian Theune]

Update of /cvs-repository/Zope3/doc/security
In directory cvs.zope.org:/tmp/cvs-serv26778

Modified Files:
	SecurityTarget.txt 
Log Message:
 - completed list of subsystems for TOE summary
 - RST corrections


=== Zope3/doc/security/SecurityTarget.txt 1.12 => 1.13 ===
--- Zope3/doc/security/SecurityTarget.txt:1.12	Thu May  6 13:09:56 2004
+++ Zope3/doc/security/SecurityTarget.txt	Thu May  6 13:14:06 2004
@@ -1036,8 +1036,7 @@
 TOE security functions
 ----------------------
 
-Zope's security functions are provided via four independent subsystems:
-
+Zope's security functions are provided via independent subsystems:
 
 - permission declarations
 
@@ -1045,7 +1044,22 @@
 
 - authentication
 
-- authorization
+- authorization (aka access)
+
+- audition
+
+- synchronization
+
+- transaction management
+
+- undo
+
+- publisher
+
+- automated tests
+
+Additionally the Python and host environment provide functionality required by
+the security functions.
 
 Definitions
 ^^^^^^^^^^^
@@ -1065,8 +1079,7 @@
 Christian
 
 The auditing subsystem
-**********************
-
+^^^^^^^^^^^^^^^^^^^^^^
 Zope provides an auditing system that listens for events within Zope according
 to the SFRs described above. It is implemented using the internal "event
 service" of Zope 3 to subscribe to the audit relevant events and log them
@@ -1079,7 +1092,7 @@
 SFRs.
 
 Events supported by Zope
-~~~~~~~~~~~~~~~~~~~~~~~~
+************************
 
 Following events are supported by Zope:
 
@@ -1126,7 +1139,7 @@
         (FMT_MSA.1, FMT_SMR.1) XXX FMT_MSA.1 is not required by minimal auditing
         
 Exceptions from the functional requirements for auditing
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+********************************************************
 
 As Zope relies on Python and the host environment to provide reliable time
 stamps, we regard auditing adjustments to the time beeing out of scope.