Comments
Newest First | Oldest First | Threaded View
But the cloud is supposed to be more secure!
Isn't that what everyone tells us? The cloud is more secure. Why worry? (sarcasm assumed)
plaintext credentials
I was hoping that we would not hear this again, plaintext credential means no credential basically.
devops-oriented world
"devops-oriented world" in which those who write the code are responsible for pushing it to production."
I do not have problem with this, therebcna still be enough chekcs to make sure no security vulnerability.
cloud providers failing to secure data centers
This is something we can argue but it is still both cloud provers and consumers to encrypt the databases. Cloud providers could make this a default features on their services.
51% web traffic
51% web traffic being not encrypted is more troubleing than database encryption at rest. So individuals who are registering those sites not having https are competely at risk.
Not surprised
This is not surprising at all. I bet it is the same on on-premises. We tend to think it is important to encrypt data but not doing that when it comes to data at rest.
What exactly is the threat vector of an unencrypted cloud database?
What exactly is the threat vector of an unencrypted cloud database? Considering this is headline I'm curious if you or anyone could describe a scenario where someone accesses data by attacking an unencrpted database. Unless I misunderstand something the encryption protects attempts to access the data at the disk level. For RDS users(the most common case) wouldn't an attacker first have to compromize AWS infrastructure to get at the disk layer of RDS? There's no public access to the disk of an RDS instance. Help me understand the risk.
Yes we encrypt our cloud databases and noticed that we have to spend more hourly on many due to the additional size requirements of encrypting them.
Yes we encrypt our cloud databases and noticed that we have to spend more hourly on many due to the additional size requirements of encrypting them.
This article and the cited report are misleading
This article, and the cited report, suggest that the 82% of unecrpyted databases in the public cloud would suddenly become safe if they were all encrpyed but that's far from the truth. This will only protect the database from an attack vector where the threat actor attempts to steal the DB in its entirety at the filesystem level. If an attack exploids weak DB credentials via an exposed port they will still have full read access to the encrypted DB unless the DB is utililzing field level encryption, which is not even mentioned in this article. The way in which the cited report collected their data is also not very scienctic; the 82% is probably not an accruate reflection of the real number. This article reads more like sponsered content than anything.
White Papers
Video
0 Comments
Current Issue
Flash Poll
The State of IT and Cybersecurity
IT and security are often viewed as different disciplines - and different departments. Find out what our survey data revealed, read the report today!
Twitter Feed
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database CVE-2018-12026
PUBLISHED: 2018-06-17
PUBLISHED: 2018-06-17
PUBLISHED: 2018-06-17
PUBLISHED: 2018-06-17
PUBLISHED: 2018-06-17
From DHS/US-CERT's National Vulnerability Database CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.
- Terms of Service
- Privacy Statement
- Legal Entities
- Copyright © 2018 UBM, All rights reserved
Tweet This
User Rank: Strategist
5/30/2017 | 9:45:46 AM
"'Average' is a statistical fiction". Under three hours average TTL for a cloud resource? Based on what? People creating something, realizing it's misconfigured, destroying it and then doing it right? Trial and error, experimentation? transient convenience builds? dynamic honeypots? the possibilities are endless and so are the questions left unanswered.
Without any discussion of the distribution curve, a single value is a data point without meaning. Imagine trying to read a graph with unlabeled axes. Pretty picture, but with what meaning?
You can do better.