Assessment Objectives
In addition to relevant policies, standards and procedures, the assessor shall examine, interview, and/or test to determine if appropriately scoped evidence exists to support the claim that:
- IAC-14_A01 the number of generations during which a password cannot be reused is specified.
Assessment rigor: 1
Origin: 171A_3.5.8[a] - IAC-14_A02 reuse of passwords is prohibited during the specified number of generations.
Assessment rigor: 1
Origin: 171A_3.5.8[b] - IAC-14_A03 an immediate change to a permanent password is required when a temporary password is used for system logon.
Assessment rigor: 1
Origin: 171A_3.5.9 - IAC-14_A04 the frequency for changing or refreshing authenticators is defined.
Assessment rigor: 1
Origin: 53A_R5_IA-05_ODP[01] 171A_R3_A.03.05.12.ODP[01] - IAC-14_A05 events that trigger the change or refreshment of authenticators are defined.
Assessment rigor: 1
Origin: 53A_R5_IA-05_ODP[02] 171A_R3_A.03.05.12.ODP[02] - IAC-14_A06 the identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution is verified.
Assessment rigor: 1
Origin: 53A_R5_IA-05a. 171A_R3_A.03.05.12.a - IAC-14_A07 initial authenticator content for any authenticators issued by the organization is established.
Assessment rigor: 1
Origin: 53A_R5_IA-05b. 171A_R3_A.03.05.12.b - IAC-14_A08 system authenticators are managed to ensure that authenticators have sufficient strength of mechanism for their intended use.
Assessment rigor: 1
Origin: 53A_R5_IA-05c. - IAC-14_A09 system authenticators are managed through the establishment and implementation of administrative procedures for initial authenticator distribution. lost, compromised or damaged authenticators. and the revocation of authenticators.
Assessment rigor: 1
Origin: 53A_R5_IA-05d. - IAC-14_A10 default authenticators are changed at first use.
Assessment rigor: 1
Origin: 53A_R5_IA-05e. 171A_R3_A.03.05.12.d - IAC-14_A11 authenticators are changed or refreshed per an organization-defined frequency or when organization-defined events occur.
Defined parameters: at least every 90 days when a password is the sole authentication factor, and immediately upon known or suspected compromise
Assessment rigor: 1
Origin: 53A_R5_IA-05f. - IAC-14_A12 system authenticators are managed through the protection of authenticator content from unauthorized disclosure and modification.
Assessment rigor: 3
Origin: 53A_R5_IA-05g. - IAC-14_A13 system authenticators are managed through the requirement for individuals to take specific controls to protect authenticators.
Assessment rigor: 3
Origin: 53A_R5_IA-05h.[01] - IAC-14_A14 system authenticators are managed through the requirement for devices to implement specific controls to protect authenticators.
Assessment rigor: 3
Origin: 53A_R5_IA-05h.[02] - IAC-14_A15 system authenticators are managed through the change of authenticators for group or role accounts when membership to those accounts changes.
Assessment rigor: 3
Origin: 53A_R5_IA-05i. - IAC-14_A16 the frequency at which to update the list of commonly used, expected or compromised passwords is defined.
Defined parameters: at least quarterly, and when new compromised password lists become available
Assessment rigor: 3
Origin: 53A_R5_IA-05(01)_ODP[01] - IAC-14_A17 authenticator composition and complexity rules are defined.
Assessment rigor: 3
Origin: 53A_R5_IA-05(01)_ODP[02] - IAC-14_A18 administrative procedures for initial authenticator distribution are established.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[01] - IAC-14_A19 administrative procedures for lost, compromised, or damaged authenticators are established.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[02] - IAC-14_A20 administrative procedures for revoking authenticators are established.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[03] - IAC-14_A21 administrative procedures for initial authenticator distribution are implemented.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[04] - IAC-14_A22 administrative procedures for lost, compromised, or damaged authenticators are implemented.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[05] - IAC-14_A23 administrative procedures for revoking authenticators are implemented.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.c[06] - IAC-14_A24 authenticator content is protected from unauthorized disclosure.
Assessment rigor: 2
Origin: SCF Created - IAC-14_A25 authenticators are changed or refreshed <A.03.05.12.ODP[01]: frequency> or when the following events occur: <A.03.05.12.ODP[02]: events>.
Defined parameters: SDP values: (1) never for passwords where MFA is employed, at least every five (5) years for hard tokens and identification badges, and at least every three (3) years for all other authenticators. (2) after a relevant security incident or any evidence of compromise or loss.
Assessment rigor: NIST 800-171
Origin: 171A_R3_A.03.05.12.e - IAC-14_A26 authenticator content is protected from unauthorized disclosure.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.f[01] - IAC-14_A27 authenticator content is protected from unauthorized modification.
Assessment rigor: 2
Origin: 171A_R3_A.03.05.12.f[02]
Linkede sager
| Linktype | Sag |
|---|---|
| blocks | Authenticator Management |
- Secure Controls Framework -
The Secure Controls Framework® (SCF)
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.