205B Cyber Security Unit 3
205B Cyber Security Unit 3
Security professionals evaluate threats and vulnerabilities based on the potential impact
they have on the confidentiality, integrity, and availability of an organization’s assets—namely, its
data, applications, and critical systems. Based on that evaluation, the security team implements a
set of security controls to reduce risk within their environment.
Confidentiality: Only authorized users and processes should be able to access or modify data
Integrity: Data should be maintained in a correct state and nobody should be able to improperly
modify it, either accidentally or maliciously
Availability: Authorized users should be able to access data whenever they need to do so
These three principles are obviously top of mind for any infosec professional. But
considering them as a triad forces security pros to do the tough work of thinking about how they
overlap and can sometimes be in opposition to one another, which can help in establishing
priorities in the implementation of security policies. We'll discuss each of these principles in more
detail in a moment, but first let's talk about the origins and importance of the triad.
Confidentiality
Confidentiality refers to an
organization’s efforts to keep their data
private or secret. In practice, it’s about
controlling access to data to prevent
unauthorized disclosure. Typically, this
involves ensuring that only those who are
authorized have access to specific assets and
that those who are unauthorized are actively
prevented from obtaining access. As an
example, only authorized Payroll employees
should have access to the employee payroll database. Furthermore, within a group of authorized
users, there may be additional, more stringent limitations on precisely which information those
authorized users are allowed to access. Another example: it’s reasonable for ecommerce customers
to expect that the personal information they provide to an organization (such as credit card, contact,
shipping, or other personal information) will be protected in a way that prevents unauthorized
access or exposure.
Many things can jeopardize availability, including hardware or software failure, power
failure, natural disasters, and human error. Perhaps the most well-known attack that threatens
availability is the denial-of-service attack, in which the performance of a system, website, web-
based application, or web-based service is intentionally and maliciously degraded, or the system
becomes completely unreachable.
Non-Repudiation
Non-repudiation is the assurance that someone cannot deny the validity of
something. Non-repudiation is a legal concept that is widely used in information security
and refers to a service, which provides proof of the origin of data and the integrity of the
data. In other words, non-repudiation makes it very difficult to successfully deny
who/where a message came from as well as the authenticity and integrity of that message.
Building on the outlined NIST phases, here are specific incident response steps
to take once a critical security event has been detected:
1. Assemble your team:
It’s critical to have the right people with the right skills, along with
associated tribal knowledge. Appoint a team leader who will have overall
responsibility for responding to the incident. This person should have a direct
line of communication with management so that important decisions—such as
taking key systems offline if necessary—can be made quickly.
In smaller organizations, or where a threat isn’t severe, your SOC team or
managed security consultants may be sufficient to handle an incident. But for the more
serious incidents, you should include other relevant areas of the company such as
corporate communications and human resources.
If you have built a Security Incident Response Team (CSIRT), now is the time
to activate your team, bringing in the entire range of pre-designated technical and non-
technical specialists.
If a breach could result in litigation, or requires public notification and
remediation, you should notify your legal department immediately.
2. Detect and ascertain the source.
The IR team you’ve assembled should first work to identify the cause of the
breach, and then ensure that it’s contained.
Security teams will become aware that an incident is occurring or has occurred
from a very wide variety of indicators, including:
Users, system administrators, network administrators, security staff, and others
from within your organization reporting signs of a security incident
SIEMs or other security products generating alerts based on analysis of log data
File integrity checking software, using hashing algorithms to detect when
important files have been altered
Anti-malware programs
Logs (including audit-related data), which should be systematically reviewed to
look at anomalous and suspicious activity with:
Users
External storage
Real-time memory
Network devices
Operating systems
Cloud services
Applications
3. Contain and recover:
An organization repeats the steps as needed to continuously assess and improve its
cybersecurity. For instance, organizations may find that more frequent repetition of the orient
step improves the quality of risk assessments. Furthermore, organizations may monitor
progress through iterative updates to the Current Profile, subsequently comparing the Current
Profile to the Target Profile. Organizations may also use this process to align their
cybersecurity program with their desired Framework Implementation Tier.
IT Goverance:
Methodology to Protect Privacy and Civil Liberties
This section describes a methodology to address individual privacy and civil liberties
implications that may result from cybersecurity. This methodology is intended to be a general
set of considerations and processes since privacy and civil liberties implications may differ by
sector or over time and organizations may address these considerations and processes with a
range of technical implementations. Nonetheless, not all activities in a cybersecurity program
engender privacy and civil liberties considerations. Technical privacy standards, guidelines,
and additional best practices may need to be developed to support improved technical
implementations.
Privacy and cybersecurity have a strong connection. An organization’s cybersecurity
activities also can create risks to privacy and civil liberties when personal information is
used, collected, processed, maintained, or disclosed. Some examples include: cybersecurity
activities that result in the over-collection or over-retention of personal information;
disclosure or use of personal information unrelated to cybersecurity activities; and
cybersecurity mitigation activities that result in denial of service or other similar potentially
adverse impacts, including some types of incident detection or monitoring that may inhibit
freedom of expression or association.
The government and its agents have a responsibility to protect civil liberties arising
from cybersecurity activities. As referenced in the methodology below, government or its
agents that own or operate critical infrastructure should have a process in place to support
compliance of cybersecurity activities with applicable privacy laws, regulations, and
Constitutional requirements.
To address privacy implications, organizations may consider how their cybersecurity
program might incorporate privacy principles such as: data minimization in the collection,
disclosure, and retention of personal information material related to the cybersecurity incident;
use limitations outside of cybersecurity activities on any information collected specifically for
cybersecurity activities; transparency for certain cybersecurity activities; individual consent
and redress for adverse impacts arising from use of personal information in cybersecurity
activities; data quality,integrity, and security; and accountability and auditing.
Governance of cybersecurity risk
An organization’s assessment of cybersecurity risk and potential risk responses
considersthe privacy implications of its cybersecurity program.
The Open Web Application Security Project ® (OWASP) is a nonprofit foundation that
works to improve the security of software. Through community-led open-source software
projects, hundreds of local chapters worldwide, tens of thousands of members, and
leading educational and training conferences, the OWASP Foundation is the source for
developers and technologists to secure the web.
For nearly two decades corporations, foundations, developers, and volunteers have supported the
OWASP Foundation and its work. Donate, Join, or become a Corporate Member today.
About the OWASP Testing Project (Parts One and Two) The OWASP is currently working on a
comprehensive Testing Framework. By the time you read this document Part One will be close
to release and Part Two will be underway. Part One of the Testing Framework describes the
Why, What, Where and When of testing the security of web applications and Part Two goes into
technical details about how to look for specific issues using source code inspection and a
penetration testing (for example exactly how to find SQL Injection flaws in code and through
penetration testing). This check list is likely to become an Appendix to Part Two of the OWASP
Testing framework along with similar check lists for source code review.