Comments
Putting Security on Par with DevOps
Newest First  |  Oldest First  |  Threaded View
allankristensen
50%
50%
allankristensen,
User Rank: Author
10/5/2018 | 9:56:27 PM
Re: Identity, Identity, Identity
Identity management is definitely a key part of building a secure public cloud infrastructure, because it's critical to control WHO can log into your public cloud environments as well as being able to ENFORCE secure login methods etc. 

However, the reality is that public cloud configuration drifts continue to happen, why it's equally important to have ongoing user credential configuration monitoring in place to avoid identity configuration drifts, such as MFA authentication not enforced, access keys not rotated, password policies not enforced, unused access keys / user ID's etc.

Furthermore, it's critical to have a solid, and automated user anomaly detection system in place to be able to distinguish between normal and unusual user activities. Public cloud environments are highly dynamic environments, and in today's world suspicious and unusual user activities, such as spinning up computing power for crypto mining activities using a compromised access key, can easily fly under the radar if User Behavior Analytics are not used efficiently to detect and alert on suspicious user activities.

The same applies to vulnerable hosts in public cloud environments. It's critical to have efficient tools in place to detect and alert on vulnerable hosts, but it's even more important to be able to correlate this information with other threat factors such as determining which vulnerable hosts has received traffic from suspicious IP addresses, and for those quickly determine the change history (what was changed and by whom). Correlated information like this will help security teams prioritize and react accordingly.

Last but not least auto-remediation capabilities are important as well, because especially for identity configuration drifts it's critical to be able to respond immediately, and without human involvement.

 

 
lunny
50%
50%
lunny,
User Rank: Strategist
10/3/2018 | 11:49:34 AM
Identity, Identity, Identity
Identity, especially non-human identities (not just the ID), must be understood.  Inventory matters, especially where assets in the cloud are more and more ephemeral and transient than ever.  Who is accessing/doing what, when are they doing it, why are they doing it, where are they doing it?  Are they authorized?  How would a threat actor compromise the identity of an asset, be it the database owner service ID, root on a server, masquerade as a trusted API interface, etc?  The concept of the right person (or non-person entity) being able to do the right thing, in the right place, at the right time, and for the right reasons is where we must start.  Along with that, the converse is important (the WRONG person/thing being able to do it).  A threat actor, especially a well-informed internal threat actor, understands the weak links in this chain and WILL exploit them.  Passwords created and known by human beings make the attacks easy.  Reference Equifax - it wasn't the Struts vulnerability; rather it was too easy to get the administrator credentials to over 50 databases once they climbed in through the bedroom window.  Humans are provably fallible in this regard.  It's not that you don't trust your privileged users, it's that you cannot.  They pick horrible passwords, share them extensively, and rarely, if ever, change them.  That grumbly Linux systems administrator who left the organization a year and a half ago still knows the passwords.  Imagine his or her ability to damage your company if so motivated.

Patching known vulnerabilities matters, monitoring for zero-day indicators matters, anti-virus/anti-malware protection matters.  But at some point, we just run out of fingers to put in the dyke.  Any organization that isn't managing identity well and taking it very seriously is whistling past the graveyard.


High Stress Levels Impacting CISOs Physically, Mentally
Jai Vijayan, Freelance writer,  2/14/2019
Valentine's Emails Laced with Gandcrab Ransomware
Kelly Sheridan, Staff Editor, Dark Reading,  2/14/2019
2018 Was Second-Most Active Year for Data Breaches
Jai Vijayan, Freelance writer,  2/13/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8948
PUBLISHED: 2019-02-20
PaperCut MF before 18.3.6 and PaperCut NG before 18.3.6 allow script injection via the user interface, aka PC-15163.
CVE-2019-8950
PUBLISHED: 2019-02-20
The backdoor account dnsekakf2$$ in /bin/login on DASAN H665 devices with firmware 1.46p1-0028 allows an attacker to login to the admin account via TELNET.
CVE-2019-8942
PUBLISHED: 2019-02-20
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring. An attacker with author privileges can execute arbitrary code by uploading a crafted image c...
CVE-2019-8943
PUBLISHED: 2019-02-20
WordPress through 5.0.3 allows Path Traversal in wp_crop_image(). An attacker (who has privileges to crop an image) can write the output image to an arbitrary directory via a filename containing two image extensions and ../ sequences, such as a filename ending with the .jpg?/../../file.jpg substring...
CVE-2019-8944
PUBLISHED: 2019-02-20
An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive Terraform output variables via log files.