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.

Perimeter

6/18/2012
09:33 AM
50%
50%

Ironman And Captain America Fight Over Compliance

Defending your company requires both warriors and soldiers

The big movie hit this year, "Marvel's The Avengers," is a fun, action-packed film. As most of you know, The Avengers are an ensemble cast of superheroes brought together to save the world when all else has failed.

A strength of this movie is the time it spends watching these superheroes as they work out their differences and learn how to work together. The movie is more a story about people, egos, and relationships than about heroes and alien attackers. How do we see ourselves? Who is important and why? Why should we work together instead of alone?

Tony Stark, a.k.a., IronMan, is an egotistical, witty genius with little regard for the rules. This, of course, rubs Captain America -- a wholesome, by-the-book soldier with a mission to follow -- the wrong way. This is similar to the personalities I see in the business world, from savvy security experts to focused compliance gurus.

Like Tony Stark (who also happens to own a company that makes weapons for defense), security experts know that the bad guys are not following the rules and are not bogged down in bureaucracy. To stop these bad guys, you have to have at least a little bad guy in you. The guys and gals focused on plans and compliance just seem to hold you back from your job of saving the planet, network, and passwords.

Captain America and the compliance experts know the value of a clearly defined plan. Without such a plan, you cannot safely coordinate the troops or the team. They all know that an every-man-for-himself strategy gets people killed or at least creates an embarrassing data breach (just ask LinkedIn). Discipline and planning (i.e., compliance) strengthen any team from those who would wish to harm it, and protect it from those within who lack the proper ethics or discipline.

Ironman and Captain America finally figured out they needed each other, as well as the rest of the Avengers, to save the Earth so the rest of us can spend our days defending networks and buying tickets to movie sequels. Their resolution was not really about compromise; each ultimately remained just as much a believer in his approach as before. No, it was about learning that to take on the really bad guys, each brings something valuable to the fight the other one needs.

To save the planet and protect your information, you need an Ironman to be the warrior and a Captain America to be the soldier. Security needs innovative warriors who still understand the value of the thoughtful compliance soldiers. These same compliance soldiers need adaptable security warriors to implement their strategies with timely tactics. To be successful, security and compliance staffs must work together to innovate within the plan while also planning to allow appropriate innovation.

If you work in security or compliance in your organization, then remember that your business world needs you to be a team. We’re counting on you, so make us proud. And let me know if you to find a good shawarma restaurant.

Glenn S. Phillips, the president of Forte' Incorporated, works with business leaders who want to leverage technology and understand the often hidden risks within. He is the author of the book Nerd-to-English, and you can find him on Twitter at @NerdToEnglish.

Glenn works with business leaders who want to leverage technology and understand the often hidden risks awaiting them. The Founder and Sr. Consultant of Forte' Incorporated, Glenn and his team work with business leaders to support growth, increase profits, and address ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
The Problem with Artificial Intelligence in Security
Dr. Leila Powell, Lead Security Data Scientist, Panaseer,  5/26/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6342
PUBLISHED: 2020-05-28
An access bypass vulnerability exists when the experimental Workspaces module in Drupal 8 core is enabled. This can be mitigated by disabling the Workspaces module. It does not affect any release other than Drupal 8.7.4.
CVE-2020-11082
PUBLISHED: 2020-05-28
In Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.
CVE-2020-5357
PUBLISHED: 2020-05-28
Dell Dock Firmware Update Utilities for Dell Client Consumer and Commercial docking stations contain an Arbitrary File Overwrite vulnerability. The vulnerability is limited to the Dell Dock Firmware Update Utilities during the time window while being executed by an administrator. During this time wi...
CVE-2020-13660
PUBLISHED: 2020-05-28
CMS Made Simple through 2.2.14 allows XSS via a crafted File Picker profile name.
CVE-2020-11079
PUBLISHED: 2020-05-28
node-dns-sync (npm module dns-sync) through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This has been fixed in 0.2.1.