Chapter 2: Understanding Identity and Access Management Flashcards
Authentication
allows entities to prove their identity by using credentials known to another entity.
Identification
occurs when a user claims or professes an identity, such as with a username, an email address, a PIV card, or by using biometrics.
Authentication
occurs when an entity provides proof of an identity (such as a password). A second identity is the authenticator and it verifies the authentication.
Authorization
provides access to resources based on a proven identity.
Accounting
methods track user activity and record the activity in logs.
Five factors of authentication are:
Something you know, such as a username and password
Something you have, such as a smart card, CAC, PIV, or token
Something you are, using biometrics, such as fingerprints or retina scans
Somewhere you are, using geolocation, a computer name, or a MAC address
Something you do, such as gestures on a touch screen
The something you know factor typically refers to
a shared secret, such as a password or a PIN. This is the least secure form of authentication.
Passwords should be
strong and changed often. Complex passwords include multiple character types. Strong passwords are complex and at least 14 characters long.
Administrators should verify
a user’s identity before resetting the user’s password. When resetting passwords manually, administrators should configure them as temporary passwords that expire after the first use, requiring users to create a new password the first time they log on. Self-service password systems automate password recovery.
Password policies provide
a technical means to ensure users employ secure password practices.
Password length specifies
the minimum number of characters in the password.
Password complexity
ensures passwords are complex and include at least three of the four character types, such as special characters.
Password history
remembers past passwords and prevents users from reusing passwords.
Minimum password age is used with password history to prevent
users from changing their password repeatedly to get back to the original password.
Maximum password age or password expiration forces users to
change their password periodically. When administrators reset user passwords, the password should expire upon first use.
Password policies should apply to
any entity using a password. This includes user accounts and accounts used by services and applications. Applications with internally created passwords should still adhere to the organization’s password policy.
Account lockout policies
lock out an account after a user enters an incorrect password too many times.
Smart cards are
credit card-sized cards that have embedded certificates used for authentication. They require a PKI to issue certificates.
Common Access Cards (CACs) and Personal Identity Verification (PIV) cards can be used as
photo IDs and as smart cards (both identification and authentication).
Tokens (or key fobs)
display numbers in an LCD. These numbers provide rolling, one-time use passwords and are synchronized with a server. USB tokens include an embedded chip and a USB connection. Generically, these are called hardware tokens.
HOTP and TOTP are
open source standards used to create one- time-use passwords.
HOTP creates a one-time-use password
that does not expire
TOTP creates a one- time password
that expires after 30 seconds.
Biometric authentication methods
are the most difficult to falsify. Physical methods include voice and facial recognition, fingerprints, retina scans, iris scans, and palm scans. Biometric methods can also be used for identification.
The false acceptance rate (FAR), or false match rate, identifies
the percentage of times false acceptance occurs.
The false rejection rate (FRR), or false nonmatch rate, identifies
the percentage of times false rejections occur.
The crossover error rate (CER) indicates
the quality of the biometric system. Lower CERs are better.
Single-factor authentication includes
one or more authentication methods in the same factor, such as a PIN and a password.
Dual-factor (or two-factor) authentication
uses two factors of authentication, such as a USB token and a PIN.
Multifactor authentication
uses two or more factors. Multifactor authentication is stronger than any form of single- factor authentication.
Authentication methods using two or more methods in the same factor are
single- factor authentication. For example, a password and a PIN are both in the something you know factor, so they only provide single-factor authentication.
Kerberos is
a network authentication protocol using tickets issued by a KDC or TGT server. If a ticket-granting ticket expires, the user might not be able to access resources. Microsoft Active Directory domains and Unix realms use Kerberos for authentication.
LDAP
specifies formats and methods to query directories. It provides a single point of management for objects, such as users and computers, in an Active Directory domain or Unix realm. The following is an example of an LDAP string: LDAP:// CN=Homer,CN=Users,DC=GetCertifiedGetAhead,DC=com
LDAP Secure (LDAPS)
encrypts transmissions with SSL or TLS.
Single sign-on (SSO)
allows users to authenticate with a single user account and access multiple resources on a network without authenticating again.
SSO can be used to
provide central authentication with a federated database and use this authentication in an environment with different operating systems (nonhomogeneous environment).
SAML is
an XML-based standard used to exchange authentication and authorization information between different parties. SAML is used with web-based applications.
A federated identity
links a user’s credentials from different networks or operating systems, but the federation treats it as one identity.
Shibboleth is
an open source federated identity solution that includes Open SAML libraries.
OAuth and OpenID Connect are
used by many web sites to streamline the authentication process for users. They allow users to log on to many web sites with another account, such as one they’ve created with Google, Facebook, PayPal, Microsoft, or Twitter.
The principle of least privilege is
a technical control that uses access controls. It specifies that individuals or processes are granted only the rights and permissions needed to perform assigned tasks or functions, but no more.
Users should not
share accounts. It prevents effective identification, authentication, authorization, and accounting. Most organizations ensure the Guest account is disabled.
Account policies often require administrators to
have two accounts (an administrator account and a standard user account) to prevent privilege escalation and other attacks.
An account disablement policy ensures
that inactive accounts are disabled. Accounts for employees who either resign or are terminated should be disabled as soon as possible. Configuring expiration dates on temporary accounts ensures they are disabled automatically.
Time restrictions can prevent users from
logging on or accessing network resources during specific hours.
Location-based policies prevent users from
logging on from certain locations.
Accounts should be recertified to
verify they are still required. For example, if the organization extends a contract, it’s a simple matter to recertify the account. Administrators verify that the contract has been extended, change the expiration date,
and enable the account.
Administrators routinely perform account maintenance. This is often done with
scripts to automate the processes and includes deleting accounts that are no longer needed.
Credential management systems
store and simplify the use of credentials for users. When users access web sites needing credentials, the system automatically retrieves the stored credentials and submits them to the web site.
The role-based access control (role-BAC) model uses
roles to grant access by placing users into roles based on their assigned jobs, functions, or tasks.
A matrix matching job titles with required privileges is useful as a planning document when using
role-BAC
Group-based privileges are a form of
role-BAC. Administrators create groups, add users to the groups, and then assign permissions to the groups. This simplifies administration because administrators do not have to assign permissions to users individually.
The rule-based access control (rule-BAC) model is based on
set of approved instructions, such as ACL rules in a firewall. Some rule- BAC implementations use rules that trigger in response to an event, such as modifying ACLs after detecting an attack.
In the discretionary access control (DAC) model,
every object has an owner. The owner has explicit access and establishes access for any other user.
Microsoft NTFS uses the
DAC model, with every object having a discretionary access control list (DACL).
The DACL identifies who has
access and what access they are granted.
A major flaw of the DAC model is its susceptibility to
Trojan horses.
Mandatory access control (MAC) uses
security or sensitivity labels to identify objects (what you’ll secure) and subjects (users). It is often used when access needs to be restricted based on a need to know. The administrator establishes access based on predefined security labels. These labels are often defined with a lattice to specify the upper and lower security boundaries.
An attribute-based access control (ABAC)
evaluates attributes and
grants access based on the value of these attributes. It is used in many software defined networks (SDNs).
