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.

Risk

8/7/2019
07:45 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Black Hat 2019: Security Culture Is Everyone's Culture

In his Black Hat USA keynote, Square's Dino Dai Zovi discussed lessons learned throughout his cybersecurity career and why culture trumps strategy.

BLACK HAT USA 2019 – Las Vegas – Cybersecurity no longer has to worry about getting attention, said Black Hat founder Jeff Moss in his introduction to the keynote that kicked off the conference's twenty-third year. Business management and political leaders recognize the importance of security; now, the infosec community must learn how to handle the spotlight.

"Not only have we got the attention, we're struggling with what we do with it – how we communicate," said Moss of the industry's present-day challenge. "The quality of communication now determines a lot of our outcomes." And while communications problems can be fixed, Moss said, doing so will require reordering the way we think and convey ideas.

His sentiment was echoed in the keynote by Dino Dai Zovi, head of mobile security at Square, who spoke about lessons learned in his career that emphasize the weight of security culture. At a time when every company is driven by software, the responsibility of security goes far beyond one team. Software teams must own security just as security must also focus on software.

Dai Zovi illustrated this idea with the story of when he started working at Square, a time he referred to as "my unfrozen caveman hacker period."

"I had no idea the depth of things I didn't know," he said.

One of those things was a cultural shift: At Square, unlike other firms, security engineers had to code like everyone else. "Because the security team wrote code like the rest of the company, there was a lot more collaboration," Dai Zovi explained. "That, I think, was really powerful."

It was one of many lessons he learned that changed the way he viewed how security influenced an organization. In his keynote, Dai Zovi outlined three additional principles for attendees to consider.

Work Backward from the Job
Before a security team can start on a project, it must first talk to internal customer teams to better understand why they're doing it in the first place. Security pros must first understand the business' struggles, what is easy for them and what adds friction, and when and why they "hired" security to do something. What are their hiring criteria? What is important to them? Just as significant is their firing criteria. What would cause them to seek an alternative solution?

"You can think about everything security does as offering a product or service to the rest of the company," Dai Zovi said. Asking these questions helps ensure security adds value rather than implements a tool or service that people didn't ask for, don't need, and likely won't use.

Seek and Apply Leverage
Many cybersecurity experts have a deep pride in being subject matter experts, Dai Zovi said, describing his second point. But this typically small group of people can have a broad impact.

"There's not enough of us," he explained, pointing to fuzzing as an example of how automation can help scale security. Making fuzzing easier for developers drives the benefit, he added, because there are more developers than there are security pros.

Dai Zovi also emphasized the importance of feedback loops. Cybercriminals have natural feedback loops; they immediately know whether things work or don't work. Defenders have to explicitly build their feedback loops, but if they do this right, they can measure attackers probing their systems, identify them learning, see them hacking, and see when they succeed.

Culture > Strategy > Tactics
"Culture is way more powerful than strategy, which is way more powerful than tactics," Dai Zovi stressed. Both operations and developers enable the business, and the business requires change. "We must allow change to happen," he added.

Businesses should move toward a model where risks are shared. Instead of security being security's job alone, organizations that can reinforce security is everyone's job can adopt a more risk-sharing culture. This is the environment Dai Zovi described at Square, where developers would write new features and go to the security team for feedback and guidance. Instead of being perceived as the "no" department, security can share their responsibility.

"Instead of saying 'no,' start with 'yes' and say, 'This is how I can help,'" Dai Zovi advised. This mindset can drive collaboration with other departments rather than isolating the security team.

"If we can create security culture change in every team, we can scale way more powerfully than we can if security is only our responsibility," he said.

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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
CVE-2019-20394
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
CVE-2019-20395
PUBLISHED: 2020-01-22
A stack consumption issue is present in libyang before v1.0-r1 due to the self-referential union type containing leafrefs. Applications that use libyang to parse untrusted input yang files may crash.