CISSP-Domain 2-Asset Security Ver 2021
CISSP-Domain 2-Asset Security Ver 2021
• Data classification is all about analyzing the data that the organization has, in whatever form, determining its
importance and value, and then assigning it to a category or classification level.
• Data classification considerations: please remember the below for exam point of view
o The value of the data to the organization, which can change over time
o The level of damage that could be caused if the data were compromised, corrupted, or damaged
o Legal, regulatory, or other responsibilities to protect the data
o Industry and the purpose/mission which the organization operates
• Classification Benefits
• Awareness among employees and customers of the organization’s commitment to protecting information.
• Identification of critical information.
• Identification of vulnerability to modification.
• Based on Value
o Assets and resources, imply value to an organization and, therefore, must be protected based on the value that it
represents to the organization.
o Value can be expressed in terms of quantitative Qualitative asset valuation implies that value is expressed in terms
of numbers
o Actual value of assets becomes very important in understanding how to protect those assets because the value will
always dictate the level of security required.
• Classification and Categorization are used to help standardize the protection baselines for information systems and
the level of suitability and trust an employee may need to access information.
• Classification Procedure
1. Define classification levels.
2. Specify the criteria that will determine how data is classified.
3. Identify data owners who will be responsible for classifying data.
4. Identify the data custodian who will be responsible for maintaining data and it security level.
5. Indicate the security controls, or protection mechanisms, required for each classification level
6. Document any exceptions to the previous classification issues.
7. Indicate the methods that can be used to transfer custody of the information to a different data owner.
8. Create a procedure to periodically review the classification and ownership.
Communicate any changes to the data custodian.
9. Indicate procedures for declassifying the data.
• Data Subject
○ Individual who is the subject of personal data
• Data Owner
○ Accountable for determining the value of the data.
○ Data owners also are accountable for defining policies for access of the data and clearly defining and
communicating the responsibilities for such protection to other entities including stewards, Custodians, and
processors.
• Data Controller
○ An entity that collects or creates PII. The data owner/controller is legally responsible
○ for the protection of the PII in their control and liable for any unauthorized release of PII.
○ Ostensibly, the owner/controller is an organization; the legal entity that legitimately owns the data.
• Data Steward
○ Data stewards are commonly responsible for data content, context, and associated business rules within the
organization.
○ Data protection officer is data steward
○ data steward is concerned with the meaning of data and the correct usage of data.
• Data Processor
○ Any entity, working on behalf or at the behest of the data controller, that processes PII. Under most PII-
related laws, “processing” can include absolutely anything that can be done with data: creating, storing,
sending, computing, compiling, copying, destroying, and so forth.
○ While the data processor does have to comply with applicable PII law, it is the data owner/controller that
remains legally liable for any unauthorized disclosure of PII even if the processor is proven to be
negligent/malicious.
• Data Custodian
○ The person/role within the organization who usually manages the data on a day-to-day basis on
○ behalf of the data owner/controller.
○ This is often a database manager or administrator; other roles that might be considered data custodians
could be system administrators or anyone with privileged access to the system or data set.
• Protect Privacy
• Privacy
o Right of the individual to control their Personal Data
o Data collection should be restricted.
Data owners have a responsibility to respect and enforce privacy principles.
• Regulation
o PIPEDA
• Personal Information Protection and Electronic Documents Act.
• Used In Canada
• Penalties need to be remember
o GDPR (https://www.nibusinessinfo.co.uk/content/data-protection-principles-under-gdpr)
• General Data Protection Regulation
• Principles set out obligations for businesses and organizations that collect, process and store
individuals' personal data. Data Breach notification: within 72 hours.
• Used in EU. Right to Erasure: All users have the “Right to be forgotten”
• Six Privacy Principle (LPD ASI)
1. Lawfulness, fairness, Transparency
2. Purpose Limitation
3. Data Minimization
4. Accuracy
5. Storage Limitation
Data sovereignty refers to legislation that covers information that is subject to the laws of the country in which
the information is located or stored
• Destroyed after its purpose is completed.
o US (Data Owner & Data Custodian)
• Retention
o Data retention, which is sometimes also referred to as records retention, is defined as the continued and long-term
storage of valuable assets.
o Companies are required to comply with legal and regulatory legislation in retaining assets, especially information
and records.
• Assets/Data Lifecycle
o To protect assets properly, one must understand the asset lifecycle and apply protection mechanisms throughout
the phases of the asset lifecycle.
o The lifecycle of data is depicted as having six phases: create, store, use, share, archive, and destroy. (CS US AD)
o Retention
• Retention is a protocol (set of rules) within an organization that dictates types of unaltered data that
must be kept and for how long.
• Legal and regulatory requirements must be considered.
• A data retention policy can help to ensure that outdated data is purged, removing potential
additional costs for discovery.
• Many organizations have aggressive retention policies to both reduce the cost of storage and limit the
amount of data that is kept on hand and discoverable.
• A well-documented policy for the retention of data is a minimum but necessary component of
regulatory compliance.
• Data retention policies are not designed to destroy incriminating data, and legal requirements for data
retention must still be met.
• The data retention policy should address what data to keep, where to keep it, how to store it, and for
how long to keep it. The policy is not concerned with “for whom” the data is kept.
o
• Legal Holding
o A legal hold is a requirement for an organization to preserve all forms of relevant information when
litigation, audit, or government investigation is reasonably anticipated.
o The objective is to avoid evidence spoliation.
o A legal hold supersedes organizational retention policies.
o eDiscovery (also called electronic discovery) refers to any process in which electronic data is sought,
located, secured, and searched with the intent of using it as evidence in a civil or criminal legal case.
o Clearing and Purging of writeable Electronic Storage Media should be performed using tools
o Destruction techniques should be used when Clearing and Purging are not effective (e.g. single-write media or media that is permanently write
protected).
o While most devices support some form of Clear, not all devices have a reliable Purge mechanism. For moderate confidentiality data, the
media owner may choose to accept the risk of applying Clear techniques to the media, acknowledging that some data may be able to be
retrieved by someone with the time, knowledge, and skills to do so.
o Purge (and Clear, where applicable) may be more appropriate than Destroy when factoring in environmental concerns, the desire to reuse
the media (either within the organization or by selling or donating the media), the cost of a media or media device, or difficulties in
physically
• Data States
o Three areas of data that must be considered in securing. Implement different types of security at all types of data.
• Data at Rest
▪ Data stored on media in any type of form. It is at rest because it is not being transmitted or processed in any way.
( Persistent Storage e.g. disk, tape)
▪ When data is at rest malicious users may
• Gain unauthorized physical or logical access to a device
• Transfer information from the device to an attacker’s system
• Perform other actions that jeopardize the confidentiality of the information on a device
▪ Data at Rest - Recommendations - Compliance - FIPS and AES.
▪ DAR Protection
CBK Notes
• A data policy that defines strategic long-term goals and provides guiding principles for data management in all aspects of a project, agency, or organization.
• A data policy that defines strategic long-term goals and provides guiding principles for data management in all aspects of a project, agency, or
organization.
• Clearly defined roles and responsibilities for those associated with the data, in particular of data providers, data owners, and custodians
• Clear and documented published data that is available and useable to users, with consistent delivery procedures.
• Data owners generally have legal rights over the data, along with copyright and intellectual property rights
• Custodianship is generally best handled by a single role or entity that is most familiar with a dataset‘s content and associated management criteria
• Quality, as applied to data, has been defined as fitness for use or potential use
• Documentation is the key to good data quality. Without good documentation, it is difficult for users to determine the fitness for use of the data and difficult for
custodians to know what and by whom data quality checks have been carried out
• Data modeling is the methodology that identifies the path to meet user requirements.
• Efforts should be made by the security practitioner to stay current on new threats so that a database and its data are not put at risk.
• Security involves the system, processes, and procedures that protect a database from unintended activity.
• Minimizing negative impact on an enterprise and the need for a sound basis in decision making are the fundamental reasons enterprises implement a risk
management process for their IT systems
• Media storing sensitive information requires physical and logical controls. The security professional must continually bear in mind that media lacks the means for
digital accountability when the data is not encrypted
• The need for media marking typically is strongest in organizations where sensitive IP and confidential data must be stored and shared amongst multiple people
• Policies and procedures describing the proper handling of sensitive media should be promulgated
• Sensitive media should not be left lying about where a passerby could access it
• Media that is no longer needed or is defective should be destroyed rather than simply disposed
• A periodic review of retained records is necessary to reduce the volume of information stored and ensure that only relevant information is preserved