2 - Access Control Policy
2 - Access Control Policy
DEPARTMENT OF EDUCATION
January 2020
Purpose
• These policies exist in addition to all other SCDE policies and federal and state
regulations governing the protection of SCDE data. Adherence to the policies will
improve the security posture of the State and help safeguard SCDE information
technology resources.
Section Overview
Each information security policy section consists of the following:
• Purpose: Provides background to each area of the information security policies.
• Policy Controls: Provides the internal policy number and the policy control.
• Policy Supplement: Contains the security solution recommendations that are connected to
the South Carolina Information Security Recommended Technology Solutions.
• Guidance: Provides references to guidelines on information security policies.
• Reference: Provides a reference to the guidance in the form of a uniform resource locator
(URL).
The purpose of the access management section is to establish processes to control access and use
of SCDE information resources. Access management incorporates role-based access controls
(RBAC), privileged-user access, access definitions, roles, and profiles.
2.102 The SCDE shall identify account types (e.g., individual, group, system,
application, guest/anonymous, and temporary) and establish conditions for
group membership.
2.103 The SCDE shall identify authorized users of the information system and specify
access rights.
2.104 The SCDE shall establish a process to enforce access requests to be approved
by business/data owner (or delegate) prior to provisioning user accounts.
2.105 The SCDE shall authorize and monitor the use of guest/anonymous and
temporary accounts and notify relevant personnel (e.g., account managers)
when temporary accounts are no longer required.
2.106 The SCDE shall establish a process to notify relevant personnel (e.g., account
managers, system administrators) to remove or deactivate access rights when
users are terminated, transferred, or access rights requirements change.
2.107 The SCDE shall remove or disable default user accounts, and, if user accounts
cannot be removed or disabled, they should be renamed.
2.108 Access shall be granted based upon the principles of need-to-know, least-
privilege, and separation of duties. Access not explicitly permitted shall be
denied by default.
2.109 Access requests from users shall be recorded and follow the SCDE-established
approval process.
2.110 The SCDE shall ensure that user access requests are approved by a business
owner (or any other pre-approved role).
2.112 The SCDE shall ensure that privileged accounts are controlled, monitored, and
can be reported on a periodic basis.
2.113 The SCDE shall regulate information system access and define security
requirements for contractors, vendors, and other service providers.
2.115 The SCDE shall enforce approved authorizations for logical access to
information systems.
2.117 For restricted data: SCDE systems shall enforce data-flow controls using
security attributes on information, source, and destination objects as a basis for
flow-control decisions.
2.120 The SCDE shall ensure that only authorized individuals have access to SCDE
data/information and that such access is strictly controlled and audited in
accordance with the concepts of “need-to-know, least-privilege, and separation
of duties”.
2.122 SCDE systems shall enforce a limit of unsuccessful logon attempts during a
SCDE-defined period. The number of logon attempts shall be commensurate
with the classification of data hosted, processed, or transferred by the
information system.
2.123 The SCDE shall automatically lock user accounts after the maximum logon
attempts is reached. The SCDE shall establish an account-lock time period
commensurate with the classification of data hosted, processed, or transferred
by the information system.
2.124 The SCDE implements warning banners that comply with federal, state, or
other laws of regulations associated with the type of data handled by the SCDE
(e.g., For FTI IRS Publication 1075 requirements apply).
2.125 The SCDE systems shall time out sessions or require a re-authentication
process after (30) minutes of inactivity.
2.204 Remote users shall connect to SCDE information systems only using
mechanism protocols approved by the SCDE through a limited number of
managed access control points for remote connections.
2.205 For restricted data and/or system administrators: SCDE employees and
authorized third parties accessing SCDE information systems remotely shall do
so via an approved two-factor authentication (2FA) technology.
2.206 The SCDE shall develop formal procedures for authorized individuals to access
its information systems from external systems, such as access allowed from an
alternate work site (if required).
2.208 The SCDE shall only use wireless networking technology that enforces user
authentication.
2.209 The SCDE shall authorize wireless access to information systems prior to
allowing use of wireless networks.
2.210 The SCDE does not allow wireless access points to be installed independently
by users.
2.211 If external systems are authorized by the SCDE, the SCDE shall establish terms
and conditions for their use, including types of applications that can be accessed
from external information systems; security category of information that can be
processed, stored, and transmitted; use of VPN and firewall technologies; the
use and protection against the vulnerabilities of wireless technologies; physical
security maintenance; and the security capabilities of installed software are to
be updated.
2.212 The SCDE networks where information deemed critical by the SCDE are stored
or processed shall be physically or logically segregated from publicly available
networks.
2.213 The SCDE networks and information systems shall not be accessible from
pubic networks (e.g., Internet) except under secured and managed interfaces
employing boundary protection devices.
2.214 The SCDE limits network access points to a minimum to enable effective
monitoring of inbound and outbound communications and network traffic.
The purpose of the identity management section is to establish a standardized method to create
and maintain verifiable user identifiers and enable decisions about the levels of access to be
given to each individual and/or groups.
2.302 The SCDE shall prevent reuse of user identifiers until all previous access
authorizations are removed from the system, including all file accesses for that
identifier.
2.303 The SCDE shall allow the use of group IDs only where these are necessary for
business or operational reasons; group IDs shall be formally approved and
documented.
2.304 If the SCDE requires group IDs, it shall require individuals to be authenticated
with a unique user account prior to using the group ID (e.g., network
authentication prior to use of Group ID).
2.305 The SCDE shall minimize the use of system, application, or service accounts;
and it shall document, formally approve, and designate a responsible party of
this type of accounts.
2.306 The SCDE security system shall be able to identify and verify the identification
and, if deemed necessary by the SCDE, the location of each authorized user.
The purpose of the authentication section is to establish the authentication methods utilized by
the SCDE for authenticating, external/remote access connections, VPN access, administrative
function access, vendor access, and remote access to sensitive information.
2.402 The SCDE shall implement mechanisms to record successful and failed
authentication attempts.
2.403 The SCDE shall define a maximum number of invalid logon attempts
commensurate to the criticality of network or information systems.
2.404 The SCDE networks and information systems shall disable user access upon
reaching the maximum number of invalid access attempts as defined by the
SCDE.
The purpose of the emergency access section is to establish conditions under which emergency
access is granted, outline rules to determine who is eligible to obtain emergency access, and
authorize personnel entitled to grant access.
The purpose of the password section is to establish uniform and enterprise-wide practices to
create, manage, and maintain passwords to ensure expected level of access security. The policy
outlines requirements for creation of strong passwords, protection of those passwords, and
password change frequency.
2.604 The SCDE must prohibit its users from using common words or personal
information as passwords (e.g., username, social security number, children’s
names, pets’ names, hobbies, anniversary dates, etc.).
2.606 The SCDE shall implement a process to change passwords immediately if there
is reason to believe a password has been compromised or disclosed to someone
other than the authorized user.
The purpose of the password administration section is to ensure that the allocation of passwords
is controlled through a formal management process.
2.702 The SCDE shall establish a process to verify the identity of a user prior to
providing a new, replacement, or temporary password.
2.703 The SCDE shall establish a process to uniquely identify and authenticate non-
Agency users.
2.704 The SCDE shall establish procedures to manage new or removed privileged-
accounts passwords.
2.705 First-time passwords shall be set to a unique value per user and changed
immediately after first use.
2.706 The SCDE shall provide temporary passwords to users in a secure manner; the
use of third parties or unprotected (i.e., clear text) electronic mail messages
shall be prohibited.
2.707 The SCDE shall obscure feedback of authentication information during the
authentication process to protect the information from possible exploitation/use
by unauthorized individuals.
2.708 The SCDE shall require that employees sign acknowledgement prior to
allowing access to network and information systems.
2.709 The SCDE shall not allow default passwords for network and remote
applications.
Policy Supplement
Refer to the SCDIS-200-InformationSecurityandPrivacyStandards030717.xlsx located in the
SCDE Info Sec policy folder.
Guidance
NIST SP 800-53 Revision 4: Security and Privacy Controls for Federal Information Systems and
Organizations