News

4/3/2017
12:03 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
100%
0%

Reactive to Proactive: 7 Principles Of Intelligence-Driven Defense

Black Hat Asia keynote speaker and Net Square CEO Saumil Shah says bug bounty programs and reactive security techniques aren't enough to protect your business.

BLACK HAT ASIA - SINGAPORE - "Bugs are around, they're going to be around forever. That's fine," admitted Net Square CEO Saumil Shah in his keynote "The Seven Axioms of Security" at Black Hat Asia 2017. This isn't because all software is buggy, he noted, but because today's technology is complex.

Shah described how each of today's systems has a nearly infinite amount of space that cybercriminals can traverse with any manner of non-architectural means.

"If you think you're going to catch them in all these combinations and permutations, you seriously need to rethink your battle," he noted.

For more than a decade and a half, the industry has primarily used a reactive approach to security, Shah explained. Businesses tried to "buy back" bugs after exploits, which led to the creation of bug bounty programs. These have become so high-stakes they are starting to backfire, Shah said, using the term "bug purchase programs." There's no end to the cost when businesses are willing to pay millions.

"We wait for things to happen and then we react," he said of today's security teams. "The industry of defending has now become largely compliance-driven." Products are marketed as solutions that reduce risk but in reality operate on three principles: rules, signatures, and updates. These are still reactive, said Shah, and they aren't enough.

"Existing defense measures do not match hacker tactics anymore," he continued. "Attackers don't follow standards and certifications. They do whatever they please."

It's time for leaders to become less reactive, and more proactive, in their approach to security, Shah explained. This is no easy feat, he said, because businesses' leaders rarely give security teams the budgets they need and usually don't understand their priorities.

To point his listeners in the right direction, Shah illustrated his call to action with seven principles security teams should adopt with the goal of intelligence-driven defense in mind: 

  • The CISO's job is to defend: CISOs should be defending and keeping systems clean. Compliance is not part of their role. Truthfully, says Shah, compliance takes up the majority of the CISO's time. It would be more effective to split the role of the CISO into two positions: a security-focused officer who prioritizes defense, and a chief compliance officer who handles the cost of doing business.
  • Intelligence begins with data collection: "There is no price you can put on historical data," said Shah. If data can be correlated, he explained, businesses should collect and save it. Start with a security data warehouse and gather data from sources of security intelligence. This may come from third-party vendors but ideally should come from the organization. "It's time that organizations who have the muscle grow their own security in-house to suit the needs of their organization," Shah emphasized. "No one product is going to fit the bill.
  • Test realistically: Systems can exist in secure and hacked states at the same time, Shah explained. You'll only know what's going on if you test, and you should test systems under real-life circumstances.
  • Keep metrics: Make a list of what is quantifiable in your process and keep metrics for them. Metrics demonstrate success and failure; they can also justify budget. You need facts to defend your strategy, Shah explained.
  • Learn from users: We can't apply the same security measures to all end users - who range from hopeless (those who tweet photos of their debit cards) to rock stars (those whom we can learn from) - Shah explained. Security leaders should identify users who are uninformed but willing to improve, and guide them to be more productive.
  • The best defense is unexpected: "Is your infosec team doing something creative every day?" Shah asked.
  • Progress should be visible: While defenses themselves should be unexpected to attackers, it's important to make protective measures visible to the business. Improve users' security knowledge and record money saved.

"If you can demonstrate money savings through defense, that's money earned," he emphasized. "It enables you to control your budget."

Related Content:

Kelly Sheridan is Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance & Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
5 Reasons the Cybersecurity Labor Shortfall Won't End Soon
Steve Morgan, Founder & CEO, Cybersecurity Ventures,  12/11/2017
BlueBorne Attack Highlights Flaws in Linux, IoT Security
Kelly Sheridan, Associate Editor, Dark Reading,  12/14/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2017
A look at the biggest news stories (so far) of 2017 that shaped the cybersecurity landscape -- from Russian hacking, ransomware's coming-out party, and voting machine vulnerabilities to the massive data breach of credit-monitoring firm Equifax.
Flash Poll
[Strategic Security Report] Cloud Security's Changing Landscape
[Strategic Security Report] Cloud Security's Changing Landscape
Cloud services are increasingly becoming the platform for mission-critical apps and data. Heres how enterprises are adapting their security strategies!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.