Policy 7230A - Department of Administration

Policy 7230A - Department of Administration Policy 7230A - Department of Administration

10.10.2014 Views

provided to all users responsible for the administration and maintenance of a system: 3.2.2.a Positional Roles Requiring Security Operations Training • The following roles types, at a minimum, require security operations training: o Roles with application implementation and/or administration responsibilities. o Roles with server implementation and/or administration responsibilities. o Roles with desktop/laptop implementation and/or administration responsibilities. o Roles with network infrastructure implementation and/or administration responsibilities. o Roles with storage infrastructure implementation and/or administration responsibilities. o Roles with security infrastructure implementation and/or administration responsibilities. 3.2.2.b Security Operations Training Frequency and Scheduling • Security operations training shall be provided for all employees with security operations responsibilities within 90 days of commencement of employment. • Security operations training shall be provided for all employees with security operations responsibilities within 90 days of the deployment of a new or significantly revised system. Where possible, employees will be trained together as groups. • Security operations training shall be provided thereafter for all employees with security responsibilities on an at least annual basis. Where possible, employees will be trained together as groups. 3.3. Maintain Records Capture documentation appropriate to all training processes: • Document and retain copies of employee completion of security awareness training. • Document and retain copies of employee completion of security operations training. Mandatory Baselines Page 6 of 25

4. Access Control These Assessment and Planning Mandatory Baselines support the Enterprise Security Policy (ITEC 7230 Rev 1) and the Default Security Requirements (ITEC 7230A). Mandatory Non-Mandatory Procedures Baselines Procedures Baselines 4. Access Control 4.1. Identification and Authentication 4.1.1. Manage Identification and Authentication (6 sets) (4 sets) 4.2. Account Management 4.2.1. Configure User Accounts (4 sets) (2 sets) 4.3. Session Management 4.3.1. Configure Systems for Secure Access (6 sets) (3 sets) 4.3.2. Configure Systems for Secure Communications (3 sets) (1 set) 4.4. Maintain Records 4.1. Identification and Authentication The following are the Mandatory Baselines that support the Identification and Authentication section of the Default Security Requirements: 4.1.1. Manage Identification and Authentication Agencies must ensure that only individuals that have the pre-established right to access systems can do so: 4.1.1.a Identity Verification • Users must be identified with government issued identifiers that include the following information: o Full name. o Signature. o Photograph. 4.1.1.b User ID Construction • User identifiers (User IDs) must be constructed in a consistent manner. 4.1.1.c User Authenticator Construction • Where passwords are used as user authenticators their length and the character sets from which they are constructed must be determined by the risk categorization of the system: o Very high and high risk systems must have passwords at least twelve characters in length that make use of all four of upper case letters, lower case letters, numbers, and special characters. o Medium risk systems must have passwords at least eight characters in length that make use of three of the Mandatory Baselines Page 7 of 25

4. Access Control<br />

These Assessment and Planning Mandatory Baselines support the Enterprise Security <strong>Policy</strong><br />

(ITEC 7230 Rev 1) and the Default Security Requirements (ITEC <strong>7230A</strong>).<br />

Mandatory<br />

Non-Mandatory<br />

Procedures Baselines Procedures Baselines<br />

4. Access Control <br />

4.1. Identification and Authentication<br />

4.1.1. Manage Identification and Authentication (6 sets) (4 sets)<br />

4.2. Account Management<br />

4.2.1. Configure User Accounts (4 sets) (2 sets)<br />

4.3. Session Management<br />

4.3.1. Configure Systems for Secure Access (6 sets) (3 sets)<br />

4.3.2. Configure Systems for Secure Communications (3 sets) (1 set)<br />

4.4. Maintain Records <br />

4.1. Identification and Authentication<br />

The following are the Mandatory Baselines that support the Identification and<br />

Authentication section <strong>of</strong> the Default Security Requirements:<br />

4.1.1. Manage Identification and Authentication<br />

Agencies must ensure that only individuals that have the pre-established right to<br />

access systems can do so:<br />

4.1.1.a Identity Verification<br />

• Users must be identified with government issued identifiers<br />

that include the following information:<br />

o Full name.<br />

o Signature.<br />

o Photograph.<br />

4.1.1.b User ID Construction<br />

• User identifiers (User IDs) must be constructed in a consistent<br />

manner.<br />

4.1.1.c User Authenticator Construction<br />

• Where passwords are used as user authenticators their length<br />

and the character sets from which they are constructed must<br />

be determined by the risk categorization <strong>of</strong> the system:<br />

o Very high and high risk systems must have passwords<br />

at least twelve characters in length that make use <strong>of</strong> all<br />

four <strong>of</strong> upper case letters, lower case letters, numbers,<br />

and special characters.<br />

o Medium risk systems must have passwords at least<br />

eight characters in length that make use <strong>of</strong> three <strong>of</strong> the<br />

Mandatory Baselines<br />

Page 7 <strong>of</strong> 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!