Systems administration team leader may outsource non-critical
components such as DNS servers.
Outsourcing should be to Members who are Assurers,
who have the appropriate technical knowledge,
and are in good contact with team leader.
</p>
<h4><aname="4.1.2">4.1.2.</a> Required staff response time </h4>
<h4><aname="4.1.2">4.1.2.</a> Required staff response time </h4>
<p>
<p>
Response times should be documented.
Response times should be documented.
@ -576,6 +590,12 @@ All changes made to system configuration must be recorded.
<h4><aname="4.2.1">4.2.1.</a> Coverage </h4>
<h4><aname="4.2.1">4.2.1.</a> Coverage </h4>
<p>
<p>
All sensitive events should be logged.
Logs should be deleted after an appropriate amount of time.
</p>
<pclass="q">
'''Move to SM:'''
Logs shall be maintained for:
Logs shall be maintained for:
</p>
</p>
@ -583,7 +603,7 @@ Logs shall be maintained for:
<li> anomalous network traffic, </li>
<li> anomalous network traffic, </li>
<li> system activities and events, </li>
<li> system activities and events, </li>
<li> application (certificate, web, mail, and database) events, </li>
<li> application (certificate, web, mail, and database) events, </li>
<li> "Comms Module" requests for certificate signing on both the cryptographic module (signing server) and the main online server, </li>
<li>'''make generic''': "Comms Module" requests for certificate signing on both the cryptographic module (signing server) and the main online server, </li>
<li> login and root access, </li>
<li> login and root access, </li>
<li> configuration changes. </li>
<li> configuration changes. </li>
</ul>
</ul>
@ -784,6 +804,10 @@ contact information needed.
<h2><aname="7">7.</a> SOFTWARE DEVELOPMENT</h2>
<h2><aname="7">7.</a> SOFTWARE DEVELOPMENT</h2>
<pclass="q">
Change name of this to Software Assessment.
</p>
<p>
<p>
Software development team is responsible
Software development team is responsible
for the security of the code.
for the security of the code.
@ -860,7 +884,9 @@ any Member that requests it.
<p>
<p>
Once signed off, software development (team leader)
Once signed off, software development (team leader)
coordinates with systems administration (team leader)
coordinates with systems administration (team leader)
to offer the patch.
to offer the upgrade.
Upgrade format is to be negotiated,
but systems administration naturally has the last word.
Software development people are not to have access
Software development people are not to have access
to the critical systems, providing a dual control
to the critical systems, providing a dual control
at the teams level.
at the teams level.
@ -877,7 +903,7 @@ system administrators.
<p>
<p>
Systems administrators copy the patches securely
Systems administrators copy the patches securely
from the repository onto the critical machine.
from the software development onto the critical machine.
See §3.3.
See §3.3.
</p>
</p>
@ -887,8 +913,29 @@ See §3.3.
<h3><aname="8.1"> 8.1. </a> Authority </h3>
<h3><aname="8.1"> 8.1. </a> Authority </h3>
<p>
<p>
The access interface is under CCS.
The software interface gives features to Support personnel.
Additions to the team are approved by Board
Access to the special features is under tight control.
Additions to the team are approved by Board,
and the software features are under CCS.
</p>
<p>
Support personnel do not have any inherent authority
to take any action,
and they have have to get authority on a case-by-case
basis.
The authority required in each case must be guided
by this policy or the Security Manual or other clear