CISSP Domain 5 - Flashcards
Introduction
- Access: Flow of information between a subject and an object
- Subject:
- Active entity that requests access to an object
- Can be a user, program or process
- Object:
- Passive entity that contains the desired information of functionality
- Access Control:
- Security feature that controls how subjects access objects
- Example: Mike needs to make a duplicate of a document on a copier, and must enter his password. Mike is the subject, the copier is the object, and the access control is the requirement to enter a password
Introduction - Access
Flow of information between a subject and an object
Introduction - Subject
- Active entity that requests access to an object
* Can be a user, program or process
Introduction - Object
Passive entity that contains the desired information of functionality
Introduction - Access Control
Security feature that controls how subjects access objects
Introduction - Example
Mike needs to make a duplicate of a document on a copier, and must enter his password. Mike is the subject, the copier is the object, and the access control is the requirement to enter a password
IAAA - Steps to Implement Access Controls
1) The subject must provide an identity
2) The subject must authenticate they are who they claim to be
3) The system validates the identity and authentication information, and then checks to see if the subject is authorized to access the object
4) The system records all activities between the subject and object for future accountability
IAAA - Logical Access Controls
Technical tools to carry out IAAA
IAAA - Identity - Definition
Uniquely represents a subject within a given environment
IAAA - Identity - Identity Attributes
- Uniqueness: Should represent something unique about the subject
- Non-descriptive: The identity name should not describe the role or purpose of the account
- Issuance: How the identity is issued to the subject (email, ID card, etc)
IAAA - Identity - Best Practices
- Each value should be unique for accountability
- A standard naming scheme should be followed
- The name should not describe the position or task
- The name should not be shared among multiple subjects
IAAA - Identity - Identity Management - Definition
The process of creating, managing and retiring identities
IAAA - Identity - Identity Management - Directories - Definition
Central locations where all subjects and objects are tracked
IAAA - Identity - Identity Management - Directories - Namespace
Hierarchical naming convention that uniquely identifies a location or object
IAAA - Identity - Identity Management - Directories - Objects in a directory
- Managed by a Directory Service
* Labeled and identified using a namespace
IAAA - Identity - Identity Management - Directories - X.500 and LDAP
- Each object:
- Common Name (CN): Identifies that object uniquely in the directory
- Distinguished Name (DN):
- Not required to be unique
- Made of Domain Components (DC’s)
- When you combine all of the DCs within a DN, you get back something that is unique in the entire directory
- X.500 directory database rules
- All objects are arranged in a hierarchical parent-child relationship
- Every object has a unique name made up of unique identifiers called ‘distinguished names’
- The supported attributes for objects are defined by a schema
IAAA - Identity - Identity Management - Directories - Meta-Directory
Aggregates information from multiple sources and presents a unified view
IAAA - Identity - Identity Management - Directories - Virtual Directory
Does not aggregate the data into its own database
IAAA - Identity - Identity Management - Web Access Management (WAM)
- Software layer that controls authentication and authorization within a web-based environment
- Most often: Associated with a Single Sign-On (SSO) experience
- Is coordinated authentication and authorization with external systems behind the scene
- Most common sequence
1) Initial authentication
2) WAM stores a cookie on the user’s computer containing some type of session identifier
3) Each web application will use WAM to retrieve this cookie and validate that it is still valid
4) If so, the user does not need to log in again - Different sub-domains cannot access each other’s cookies
IAAA - Authentication - Introduction
- Definition: Process of the subject proving it is who it claims to be
- 4 attributes for any authentication mechanism
- Transparent: User should not be aware of it
- Scalable: Not to create bottlenecks
- Reliable: No single point of failure
- Secure: Provides authentication and confidentiality
IAAA - Authentication - Factors
1) Something a person knows
2) Something a person has
3) Something a person is
IAAA - Authentication - Factors - 1) Something a person knows
- Examples: Password, PIN, Lock combination
* Risk: An attacker could acquire this knowledge
IAAA - Authentication - Factors - 2) Something a person has
- Examples: Swipe card, Smart token, Keys, Access badge
* Risk: An attacker could steal this
IAAA - Authentication - Factors - 3) Something a person is
- Examples: Fingerprint, Retina pattern, Gait, Voice print
* Risk: An attacker could physically emulate this