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 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
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-5065
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5066
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2018-5067
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Heap Overflow vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
CVE-2018-5068
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2018-5069
PUBLISHED: 2018-07-20
Adobe Acrobat and Reader 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have an Out-of-bounds write vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.