Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

5/3/2018
07:24 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

RSA CTO: 'Modernization Can Breed Malice'

Zulfikar Ramzan predicted the future of cybersecurity, drivers shaping it, and how enterprise IT should react in his InteropITX 2018 keynote.

InteropITX 2018 — Las Vegas — In a room packed with business technology executives, RSA CTO Zulfikar Ramzan discussed the reality of today's cybersecurity landscape and the threats IT organizations should have at top of mind as they adopt new tech like machine learning.

"No organization exists as an isolated entity," said Ramzan in his keynote presentation. "The ripples of chaos can spread farther and faster now, as technology connects us in remarkably astonishing ways … in cybersecurity, they're quite prevalent."

To illustrate his point, he cited several recent security incidents that expanded far beyond players' expectations. The Target breach, one of the largest in history, happened because threat actors accessed a single password for a third-party HVAC system. Makers of baby cameras became entities in a massive DDoS attack that resulted in the takedown of major websites. An attack on the DNC caused people to question the foundations of democracy, he said.

Now, board members can see their careers fall apart following a cyber incident. In a world like that, Ramzan noted, we need to think less about security trends and more about the drivers: modernization of technology, malice of threat actors, and mandates forcing organizations to tie their business value to the strength of their security posture.

"Innovation can invite exploitation. Modernization can breed malice," Ramzan said.

Consider the evolution of ransomware, a comparatively old threat that has grown with the modernization of payment technology. The advent of digital payment systems has given attackers the means to collect more money from increasingly large groups of victims. Some hackers couple their attacks with 24/7 customer support to help their victims pay up.

"When threat actors start talking about customer support, we are in a brand-new world," explained Ramzan, who calls this mindset the "hacker industrial complex." It's not only the advanced actors his audience will have to worry about either, but the average attackers who are happy to do "a simple smash-and-grab" to generate a lot of money in a short timeframe.

Ramzan turned the conversation to artificial intelligence and machine learning, two hot topics of conversation among the InteropITX enterprise audience. AI has been around for a long time, and it has been used in the context of security for a long time, he explained. It's used to combat spam, online fraud, malicious software and malware, and malicious network traffic.

"But we're just at the beginning of what AI can actually do," he continued.

(Image: Interop)

(Image: Interop)

What worries Ramzan about AI and machine learning is putting all data in one place for technology to analyze it. It's not the theft of data that concerns him, but the manipulation of that data. If a threat actor can access and modify an organization's data, chances are nobody will notice it. Few people understand the mathematics of how these technologies work.

"Machine learning wasn't designed to deal with threat actors," he explained. "But if you're going to think about technology becoming ubiquitous, you have to think about the risks."

But how to address the risks? Ramzan warned of the danger in adopting a "no vendor left behind" policy when shopping for security tools. The industry "is effectively a hot mess," he said. With some 2,000 vendors in the security space, there is a need to consolidate and innovate. IT pros should figure out which vendors provide the most value, and focus on them.

He closed out his keynote by explaining how to react when security incidents occur. "Plan for the chaos you can't control," he noted, pointing to the "ABCs" of incident response planning.

The first: Availability. When forming an incident response plan, you should only use resources that are already available to your organization. "An incident response plan isn't a wish list," said Ramzan. "Don't put empty fire extinguishers in every hallway."

Budget is second. Security breaches come with unexpected costs, he noted. You may need legal help, for example, and if you don't have an in-house team you'll need to hire an outside law firm. "Response plans must have budget authority," said Ramzan. Without them, "effectively, it's just a fairy tale."

The final factor is Collaboration. During an incident, most areas of an organization can inevitably get involved. Security teams will be identifying the root cause of the attack while the IT team patches infrastructure and quarantines networks. If customers were affected then the sales team will be involved; if sales is involved, then the marketing team may be involved also.

Success in cybersecurity will depend on enterprise ability to gauge the risks that lie ahead, he concluded. "Adapt quickly and adopt technology in a way that fosters and fuels innovation."

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Human Nature vs. AI: A False Dichotomy?
John McClurg, Sr. VP & CISO, BlackBerry,  11/18/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3350
PUBLISHED: 2019-11-19
masqmail 0.2.21 through 0.2.30 improperly calls seteuid() in src/log.c and src/masqmail.c that results in improper privilege dropping.
CVE-2011-3352
PUBLISHED: 2019-11-19
Zikula 1.3.0 build #3168 and probably prior has XSS flaw due to improper sanitization of the 'themename' parameter by setting default, modifying and deleting themes. A remote attacker with Zikula administrator privilege could use this flaw to execute arbitrary HTML or web script code in the context ...
CVE-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.