Policy 7230A - Department of Administration
Policy 7230A - Department of Administration Policy 7230A - Department of Administration
4. Access Control These Assessment and Planning Mandatory Procedures support the Enterprise Security Policy (ITEC 7230 Rev 1). 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 Procedures that support the Identification and Authentication section of the Default Security Requirements: 4.1.1. Manage Identification and Authentication Agencies should ensure that only individuals that have the pre-established right to access systems can do so: 4.1.1.1 Verify User Identity To ensure that system accounts are only extended to known and trusted individuals, these individuals must be fully identified via external identity verification methods prior to the issuance of accounts: • As part of the on-boarding process, employee identity should be verified through the use of government-issued identification documents. • As part of the visitor verification process, where visitors may be provided with system access, visitor identity should be verified through the use of government-issued identification documents. 4.1.1.2 Create Unique IDs and Authenticators Each system user is to be provided with an identifier (also known as identity or ID) and an authenticator such that they can uniquely and individually access the system: • Identifiers must be unique to the individual but can be common across systems. • Authenticators must be unique to each individual and to each systems; however a master authenticator may be used to 9
access individual system authenticators (a single sign-on system). 4.1.1.3 Securely Distribute IDs and Authenticators The identifiers and authenticators associated with each account must be distributed in such a manner as to ensure they are delivered only to the personnel to whom they are assigned: • Identifiers are to be distributed in a manner that eliminates repudiation of receipt. • Authenticators are to be distributed in a manner that protects their secrecy and eliminates repudiation of receipt. 4.1.1.4 Provide Lifespan Management for Authenticators Over time, authenticators can become known (if they are first factor authenticators), or inactive/damaged/lost (if they are second factor authenticators) and so must be continually managed: • First factor authenticators will be provided with both a maximum and minimum lifespan and may be reset at any time at the request of the employee according to established Standards. • Second factor authenticators will be replaced at such point as they are lost, damaged, or fail. 4.1.1.5 Disable and Archive Inactive Identifiers Once an identifier is no longer required, it must be disabled to prevent its use and archived to provide for potential future investigation: • Where account access is still required by any person, identifiers will be reset. • Where account access is no longer required, identifiers will be deleted along with the account. 4.1.1.6 Revoke Inactive Authenticators Authenticators that have become known, are lost/damaged/inactive or are simply no longer required must be revoked to eliminate the potential of them being used to suborn access: • Where account access is still required by any person, first factor authenticators will be reset. • Where account access is no longer required, first factor authenticators will be deleted along with the account. • Second factor authenticators will be disassociated with accounts and returned to the inactive authenticator pool. 4.2. Account Management No applicable Mandatory Procedures. 10
- Page 17 and 18: potential exists that legitimate us
- Page 19 and 20: 5 Systems Configuration Sections 5.
- Page 21 and 22: Collaborative computing infrastruct
- Page 23 and 24: Where data requires encryption, tha
- Page 25 and 26: 6 Systems Operation Sections 6.1, 6
- Page 27 and 28: Only pre-approved maintenance tools
- Page 29 and 30: ecorded logs. In the event of other
- Page 31 and 32: event that an incident occurs, the
- Page 33 and 34: 9.2 Contingency Infrastructure The
- Page 35 and 36: 10 Physical Security Sections 10.1
- Page 37 and 38: automatically shall notify appropri
- Page 39 and 40: copy of the signed document will be
- Page 41 and 42: 12 Secure Purchasing/Acquisition Se
- Page 43 and 44: CA-1 Certification, Accreditation,
- Page 45 and 46: PE-18 Location of Information Syste
- Page 47 and 48: Appendix B - Matrix of Responsibili
- Page 49 and 50: Part 2 - Non-IT Roles (See Page 3 f
- Page 51 and 52: Appendix C - Supporting Document Cr
- Page 53 and 54: Mandatory Non-Mandatory Procedures
- Page 55 and 56: Integrity The second of the three g
- Page 57 and 58: State of Kansas Mandatory Procedure
- Page 59 and 60: 6.2. Integrity Operations .........
- Page 61 and 62: 2. Assessment & Security Planning T
- Page 63 and 64: 2.2. Create a Security Plan No appl
- Page 65 and 66: 3.1.1.2 Create Training Materials O
- Page 67: Operations Training is defined as t
- Page 71 and 72: 5. Systems Configuration These Syst
- Page 73 and 74: 5.3.1.3 Restrict Access to Media No
- Page 75 and 76: • When no longer required, data s
- Page 77 and 78: 8. Incident Response These Incident
- Page 79 and 80: Capture documentation appropriate t
- Page 81 and 82: Different types of disruptions requ
- Page 83 and 84: 9.3.2.1 Perform System Backup Back
- Page 85 and 86: 11. Personnel Security These Person
- Page 87 and 88: 12. Secure Purchasing/Acquisition N
- Page 89 and 90: Table of Contents Introduction ....
- Page 91 and 92: Introduction This Mandatory Baselin
- Page 93 and 94: 2.1.2.c Information Protection •
- Page 95 and 96: o Appropriate physical security mea
- Page 97 and 98: 4. Access Control These Assessment
- Page 99 and 100: 5. Systems Configuration These Syst
- Page 101 and 102: 5.3.1.c Media Disposal Methods •
- Page 103 and 104: 6.4. Maintain Records Agencies must
- Page 105 and 106: 8. Incident Response These Incident
- Page 107 and 108: 9.1.1.c Contingency Plan Update Fre
- Page 109 and 110: Mandatory Baselines • Systems man
- Page 111 and 112: 10. Physical Security No applicable
- Page 113 and 114: • Data is to be used for its inte
- Page 115 and 116: State of Kansas Non-Mandatory Proce
- Page 117 and 118: 6.3. Maintenance Operations .......
access individual system authenticators (a single sign-on<br />
system).<br />
4.1.1.3 Securely Distribute IDs and Authenticators<br />
The identifiers and authenticators associated with each account must<br />
be distributed in such a manner as to ensure they are delivered only<br />
to the personnel to whom they are assigned:<br />
• Identifiers are to be distributed in a manner that eliminates<br />
repudiation <strong>of</strong> receipt.<br />
• Authenticators are to be distributed in a manner that protects<br />
their secrecy and eliminates repudiation <strong>of</strong> receipt.<br />
4.1.1.4 Provide Lifespan Management for Authenticators<br />
Over time, authenticators can become known (if they are first factor<br />
authenticators), or inactive/damaged/lost (if they are second factor<br />
authenticators) and so must be continually managed:<br />
• First factor authenticators will be provided with both a<br />
maximum and minimum lifespan and may be reset at any time<br />
at the request <strong>of</strong> the employee according to established<br />
Standards.<br />
• Second factor authenticators will be replaced at such point as<br />
they are lost, damaged, or fail.<br />
4.1.1.5 Disable and Archive Inactive Identifiers<br />
Once an identifier is no longer required, it must be disabled to<br />
prevent its use and archived to provide for potential future<br />
investigation:<br />
• Where account access is still required by any person,<br />
identifiers will be reset.<br />
• Where account access is no longer required, identifiers will be<br />
deleted along with the account.<br />
4.1.1.6 Revoke Inactive Authenticators<br />
Authenticators that have become known, are lost/damaged/inactive<br />
or are simply no longer required must be revoked to eliminate the<br />
potential <strong>of</strong> them being used to suborn access:<br />
• Where account access is still required by any person, first<br />
factor authenticators will be reset.<br />
• Where account access is no longer required, first factor<br />
authenticators will be deleted along with the account.<br />
• Second factor authenticators will be disassociated with<br />
accounts and returned to the inactive authenticator pool.<br />
4.2. Account Management<br />
No applicable Mandatory Procedures.<br />
10
Change language