Data Security issues, threats , CIA Triad
Data Security issues, threats , CIA Triad
Confidentiality
For example, those who work with an organization’s finances should be able to
access the spreadsheets, bank accounts, and other information related to the
flow of money. However, the vast majority of other employees—and perhaps
even certain executives—may not be granted access. To ensure these policies
are followed, stringent restrictions have to be in place to limit who can see
what.
There are several ways confidentiality can be compromised. This may involve
direct attacks aimed at gaining access to systems the attacker does not have
the rights to see. It can also involve an attacker making a direct attempt to
infiltrate an application or database so they can take data or alter it.
To fight against confidentiality breaches, you can classify and label restricted
data, enable access control policies, encrypt data, and use multi-factor
authentication (MFA) systems. It is also advisable to ensure that all in the
organization have the training and knowledge they need to recognize the
dangers and avoid them.
Integrity
Integrity involves making sure your data is trustworthy and free from
tampering. The integrity of your data is maintained only if the data is
authentic, accurate, and reliable.
To protect the integrity of your data, you can use hashing, encryption, digital
certificates, or digital signatures. For websites, you can employ trustworthy
certificate authorities (CAs) that verify the authenticity of your website so
visitors know they are getting the site they intended to visit.
Availability
Even if data is kept confidential and its integrity maintained, it is often useless
unless it is available to those in the organization and the customers they serve.
This means that systems, networks, and applications must be functioning as
they should and when they should. Also, individuals with access to specific
information must be able to consume it when they need to, and getting to the
data should not take an inordinate amount of time.
If, for example, there is a power outage and there is no disaster recovery
system in place to help users regain access to critical systems, availability will
be compromised. Also, a natural disaster like a flood or even a severe
snowstorm may prevent users from getting to the office, which can interrupt
the availability of their workstations and other devices that provide business-
critical information or applications. Availability can also be compromised
through deliberate acts of sabotage, such as the use of denial-of-service (DoS)
attacks or ransomware.
The CIA triad provides a simple yet comprehensive high-level checklist for the
evaluation of your security procedures and tools. An effective system satisfies
all three components: confidentiality, integrity, and availability. An information
security system that is lacking in one of the three aspects of the CIA triad is
insufficient.
The CIA security triad is also valuable in assessing what went wrong—and what
worked—after a negative incident. For example, perhaps availability was
compromised after a malware attack such as ransomware, but the systems in
place were still able to maintain the confidentiality of important information.
This data can be used to address weak points and replicate successful policies
and implementations.
You should use the CIA triad in the majority of security situations, particularly
because each component is critical. However, it is particularly helpful when
developing systems around data classification and managing permissions and
access privileges. You should also stringently employ the CIA triad when
addressing the cyber vulnerabilities of your organization. It can be a powerful
tool in disrupting the Cyber Kill Chain, which refers to the process of targeting
and executing a cyberattack. The CIA security triad can help you hone in on
what attackers may be after and then implement policies and tools to
adequately protect those assets.
In addition, the CIA triad can be used when training employees regarding
cybersecurity. You can use hypothetical scenarios or real-life case studies to
help employees think in terms of the maintenance of confidentiality, integrity,
and availability of information and systems.
Data breaches
When the safety of data is compromised within the cloud, this can lead to
attacks such as leaked data. If the cloud service – or a connected device – is
breached, sensitive data has been accessed. If a cyber criminal has access to
this information, they could choose to distribute it. When the data in storage is
transferred, either electronically or physically, it becomes leaked. As the cloud
does not use hardware, cyber criminals can leak cloud data online or by
remembering information and distributing it later. Also known as low and slow
data theft, data leakage is a common danger in cloud computing.
Data Loss
Another common cloud storage security risk is data loss. As opposed to
information being stolen and distributed, it is erased entirely. This could either
be the result of hacking, a virus or a system failure – this poses an issue when
data is not backed up, highlighting the importance of securing cloud services.
However, if a cyber criminal is targeting specific data, they may target the
backup as well.
Data loss can be damaging for a business – the information can be difficult or
impossible to recover, and you may find recovery attempts use a lot of time,
money and resources. Some data may have to be recreated, and others may
be found in hard copy formats that need converting. Data loss can be very
disruptive to workflow.
Cryptojacking
While cryptomining is legal, this mining activity can then use up a lot of
resources, hence why cyber criminals opt to mine on devices that aren’t theirs.
You may find you have higher electricity bills, lower battery life and slower
processes. Cryptomining can be a profitable business, however, in order to be
successful; you will likely have to spend a lot in advance on the resources you
use.
Traditional security measures tend to focus on external threats and are not
always capable of identifying an internal threat emanating from inside the
organization.
You can take the following steps to help reduce the risk of insider threats:
Insider threats can be harder to identify or prevent than outside attacks, and
they are invisible to traditional security solutions like firewalls and intrusion
detection systems, which focus on external threats. If an attacker exploits an
authorized login, the security mechanisms in place may not identify the
abnormal behavior. Moreover, malicious insiders can more easily avoid
detection if they are familiar with the security measures of an organization.
To protect all your assets, you should diversify your insider threat detection
strategy, instead of relying on a single solution. An effective insider threat
detection system combines several tools to not only monitor insider behavior,
but also filter through the large number of alerts and eliminate false positives.
Tools like Machine Learning (ML) applications can help analyze the data stream
and prioritize the most relevant alerts. You can use digital forensics and
analytics tools like User and Event Behavior Analytics (UEBA) to help detect,
analyze, and alert the security team to any potential insider threats.
User behavior analytics can establish a baseline for normal data access activity,
while database activity monitoring can help identify policy violations.
Denial of services
1. Application-layer Flood
In this attack type, an attacker simply floods the service with requests from a
spoofed IP address in an attempt to slow or crash the service, illustrated in .
This could take the form of millions of requests per second or a few thousand
requests to a particularly resource-intensive service that eat up resources until
the service is unable to continue processing the requests.
DDoS attacks are famously hard to mitigate, which is why outsourcing network
filtering to a third party is the recommended approach. We'll cover this later
on.
Not all DoS attacks are nefarious. The third attack type is the "unintended"
Denial of Service attack. The canonical example of an unintended DDoS is
called "The Slashdot Effect (opens new window)". Slashdot is an internet news
site where anyone can post news stories and link to other sites. If a linked story
becomes popular, it can cause millions of users to visit the site overloading the
site with requests. If the site isn't built to handle that kind of load, the
increased traffic can slow or even crash the linked site. Reddit and "The Reddit
Hug of Death (opens new window)" is another excellent example of an
unintentional DoS.
The only way to prevent these types of unintended DoS attacks is to architect
your application for scale. Use patterns like edge-caching with CDNs, HTTP
caching headers, auto-scaling groups, and other methods to ensure that even
when you receive a large amount of burst-traffic, your site will not go down.
Another type of unintentional DoS attack can occur when servicing low
bandwidth areas. For instance, streaming content internationally means that
people in certain areas of the world with slow or bad internet connections
might cause problems. When your service attempts to send information to
these low-bandwidth areas, packets drop. In an attempt to get the information
to the destination, your service will attempt to resend all dropped packets. If
the connection drops the packets again, your service may make another
attempt. This cycle can cause your service's load to double or triple, causing
your service to be slow or unreachable for everyone.