Policy 7230A - Department of Administration

More documents

Recommendations

Info

authenticators for critical information systems must not be provided together while identifiers and authenticators for non-critical information systems should not be provided together. In circumstances where authentication must be cryptographically protected, the solution that provides this functionality must meet the minimum specifications of FIPS 140-2. Should an information system user’s account be disabled for any reason (see section 4.2, Account Management) the users identifier and authenticator will also be disabled, where applicable. A. Passwords Passwords form the primary means of authentication for the State of Kansas. To ensure that passwords present as much security as possible, the following restrictions apply to them: • Passwords must be constructed according to set requirements. • Passwords will have both minimum and maximum lifespan. • Passwords may not be reused for a set number of generations. • Passwords may not be displayed while they are being entered. • Password should not be transmitted in clear text. • Passwords are to be individually owned and kept confidential – they are not to be shared. • If passwords must be electronically stored, they cannot be stored in clear text. Guidelines for these requirements will be provided in a separate document. B. Authentication Tokens Though the State does not, as a rule, require the use of hardware tokens for authentication purposes, in those circumstances where the choice is made to use them, the following restrictions apply: • A defined process must be followed for token distribution. • A defined process must be followed for token revocation. • A defined process must be followed for the handling of lost/stolen/damaged tokens. Guidelines for these requirements will be provided in a separate document. 4.2 Account Management The State of Kansas requires that all information system accounts be actively managed by appropriate administrative staff. Active management includes the acts of establishing, activating, modifying, disabling and removing accounts from information systems. Information system accounts are the only legitimate method by which State information systems may be accessed. Without active account management, the 12
potential exists that legitimate users can use these accounts for illegitimate purposes. Additionally, the potential exists that these accounts can be usurped and used illegitimately to access State information systems. Information system accounts are to be constructed such that they enforce the most restrictive set of rights/privileges or accesses required for the performance of tasks associated with that account. Further, accounts shall be created such that no-one account can authorize, perform, review and audit a single transaction to eliminate conflicts of interest. Information system accounts are to be reviewed to identify accounts with inappropriate privileges (either too high or too low) on at least an annual basis. Should information system accounts be discovered with inappropriate privileges those privileges will be manually reset to the established level. Information systems accounts are to be reviewed to identify inactive accounts. Should information system accounts that are associated with an employee or third party be discovered that have been inactive for a significant period of time, the owners of the account will be notified of pending disablement. Should the account continue to remain inactive it will be manually disabled. Inactive accounts that are not associated with an employee or third party but are associated with a system process (such as inter-system information transfer) that has been explicitly logged will not be disabled but will be reviewed on an annual basis. Inactive accounts that are not associated with employees, third parties, or system processes (including those that have not been explicitly logged) will be manually disabled. Login attempts to information systems will be restricted such that after a set number of failed attempts within a pre-defined period of time, they will be locked out. Lockout will be automatically lifted after a pre-defined period of time or may be manually lifted through a pre-defined process. 4.3 Session Management The State of Kansas requires that all communications sessions with information systems be both authenticated and actively managed by administrative staff. Active management includes the acts of monitoring, suspending, disabling and terminating communications to and from information systems. Communications between components of information systems or between information systems themselves involve the transmission of information making that information susceptible to attack. Without session management, the potential exists that communications can be established or used illegitimately thereby exposing State information to an increased likelihood of loss or corruption. All State information systems will display a system use notification that indicates that the user is accessing a State of Kansas information system; that system usage is monitored, recorded and subject to audit; that unauthorized use is prohibited and subject to punitive action; that use of the information system implies consent to these 13
Page 1 and 2: State of Kansas Kansas Information
Page 3 and 4: Table of Contents Introduction ....
Page 5 and 6: Introduction This Security Requirem
Page 7 and 8: • It will ensure that privileged
Page 9 and 10: G. Security Administrators Security
Page 11 and 12: 2 Assessment & Security Planning Se
Page 13 and 14: 3 Awareness & Training Section 3.1
Page 15: 4 Access Control Sections 4.1, 4.2,
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 and 68:
Operations Training is defined as t
Page 69 and 70:
access individual system authentica
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:
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 .......
Page 119 and 120:
Introduction This Non-Mandatory Pro
Page 121 and 122:
2.1.1.4 Likelihood Determination Es
Page 123 and 124:
2.2.1.5 Establish Appropriate Secur
Page 125 and 126:
Page 127 and 128:
4.3. Session Management The followi
Page 129 and 130:
4.3.2.2 Restrict Intra and Inter-Sy
Page 131 and 132:
5.1.1.3 Actively Maintain Inventory
Page 133 and 134:
5.1.3.3 Provide Implementation Docu
Page 135 and 136:
• Place all media in a locked con
Page 137 and 138:
6. Systems Operation These Systems
Page 139 and 140:
6.2. Integrity Operations The follo
Page 141 and 142:
6.3.2. Perform Patch and Vulnerabil
Page 143 and 144:
6.4. Maintain Records Agencies shou
Page 145 and 146:
7.1.1.3 Require Authenticated Acces
Page 147 and 148:
Page 149 and 150:
8.1.2.2 Develop Supporting Strategi
Page 151 and 152:
9. Contingency Planning No applicab
Page 153 and 154:
10.1.1.2 Implement Physical Access
Page 155 and 156:
Page 157 and 158:
• Review created accounts and ass
Page 159 and 160:
11.2.4.3 Recover all Organizational
Page 161 and 162:
12.1.1.3 Required Test and Validati
Page 163 and 164:
State of Kansas Non-Mandatory Basel
Page 165 and 166:
6.2. Integrity Operations .........
Page 167 and 168:
Introduction This Non-Mandatory Bas
Page 169 and 170:
• High risk constitutes high like
Page 171 and 172:
2.3. Maintain Records Agencies shou
Page 173 and 174:
Page 175 and 176:
• Systems that have very high ris
Page 177 and 178:
5.1.1.c System and Component Docume
Page 179 and 180:
5.2. Systems Protection No applicab
Page 181 and 182:
o Passwords in the clear. o Violati
Page 183 and 184:
o Penetration testing. o Password c
Page 185 and 186:
o The individuals to be notified. o
Page 187 and 188:
7. Systems Audit These Systems Audi
Page 189 and 190:
eviewed weekly and every system and
Page 191 and 192:
8.1.1.b IR Roles • IR Team Manage
Page 193 and 194:
8.1.2.e IR Plan Update Scheduling a
Page 195 and 196:
10. Physical Security These Physica
Page 197 and 198:
10.2.1.b Power Delivery Specificati
Page 199 and 200:
Page 201 and 202:
11.2.2. Hire Employees in a Structu
show all

Policy 7230A - Department of Administration

Create successful ePaper yourself

Delete template?

Save as template?