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

9/13/2019
10:00 AM
Joshua Goldfarb
Joshua Goldfarb
Commentary
Connect Directly
Twitter
RSS
E-Mail vvv
100%
0%

Taking a Fresh Look at Security Ops: 10 Tips

Maybe you love your executive team, your security processes, tools, or strategy. Maybe you hate them. Whatever the situation, it's likely at some point that things will have changed.

A few months back, someone asked me to help him take apart a bed frame. He had a problem stemming from a stripped screw that could not be removed. When I came over, I noticed another screw on the other arm of the bracket. The second screw was not stripped, and so I loosened it. This freed the bracket, which allowed me to easily take apart the bed frame.

I'm relaying this incident not to brag about my talent as a brilliant problem solver or because I am exceptionally handy. In fact, the person who asked me for help is a particularly brilliant problem solver — a far better one than I. The reason I was able to solve the bed frame problem is because I looked at it with fresh eyes, a state of mind that is also useful in the realm of cybersecurity, as these 10 examples demonstrate:

  1. Executive support: Struggling to get the attention of executives and the board? Not able to make security a priority for the business and advance items important to security? Try looking at the problem through new eyes — namely theirs. How do executives view the business? What risks and threats to the business are they concerned with? If you can view issues from the perspective of the C-suite, you might have better luck communicating why security is important in a language they'll understand far better.
  2. Security strategy: Sure, you may have a formal security strategy that was written a few years back. But have you looked at it with your present-day eyes? The environment in which the security team operates changes constantly. It might be time to take a fresh look at the overall direction of the program.
  3. Risk: Do you understand the risks that the business faces? Are you sure? Risks evolve continuously and understanding what they are and how they affect the business today is paramount to successfully securing the business.
  4. Threats: Are you familiar with the information security threat landscape that you face? Are you certain that your knowledge is up to date? It might be time to take a new look at the threat landscape as it pertains to your enterprise.
  5. Goals: When was the last time you set goals for the security team? Was it at a time when you may have looked at the information security world differently? If the last time you examined goals was not so recently, you will likely see the topic differently now. Give goals a glance through your present-day eyes.
  6. Priorities: The security team's priorities are likely shifting constantly. New challenges arise continuously, as do old challenges. So why is it that you set priorities only once per year, or even less frequently than that? Of course, priorities cannot be reset daily, but there is a balance here. Try looking at priorities more frequently than annually.
  7. People: You're likely quite fond of and proud of the security team you've built. You've probably assembled a group of skilled and talented contributors. But there is more to the equation than just the quality of the team you've put together. There is also consideration of the alignment of the team and their skill sets to your strategic objectives. Has it been a while since you took a look at your team from that perspective? It might be worth a new look.
  8. Process: I've seen my share of bad processes over the course of my career. Even the good processes I've come across were written for a given purpose under a specific set of circumstances. What if the purpose and/or the circumstances change? Over a period of time, this is almost always the case. Given that, doesn't it make sense to reevaluate whether or not different processes make sense in the current environment? Casting a fresh look upon processes often produces more effective and efficient ones.
  9. Technology: Maybe you love your security tooling. Maybe you hate it. Maybe you painstakingly architected your security stack with an eye for detail. Maybe you inherited some or all of it. Whatever the situation, it's likely that things have changed quite a bit since the tooling in place was procured and deployed. Isn't it time to ensure that the technology in place still fits the bill? My guess is that you'll find several pieces that are no longer appropriate.
  10. External organizations: You probably have a membership in a few different external organizations. Perhaps you are a part of mailing lists, attend conference calls, or participate in meetings with these organizations on a fairly regular basis. When was the last time you stopped to think about what you're actually getting out of these organizations versus what you're putting into them? What once made sense may no longer be the case. Definitely worth a glance with fresh eyes.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "Escaping Email: Unlocking Message Security for SMS, WhatsApp"

Josh (Twitter: @ananalytical) is an experienced information security leader who works with enterprises to mature and improve their enterprise security programs.  Previously, Josh served as VP, CTO - Emerging Technologies at FireEye and as Chief Security Officer for ... 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 6/5/2020
How AI and Automation Can Help Bridge the Cybersecurity Talent Gap
Peter Barker, Chief Product Officer at ForgeRock,  6/1/2020
Cybersecurity Spending Hits 'Temporary Pause' Amid Pandemic
Kelly Jackson Higgins, Executive Editor at Dark Reading,  6/2/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: What? IT said I needed virus protection!
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-2020-13864
PUBLISHED: 2020-06-05
The Elementor Page Builder plugin before 2.9.9 for WordPress suffers from a stored XSS vulnerability. An author user can create posts that result in a stored XSS by using a crafted payload in custom links.
CVE-2020-13865
PUBLISHED: 2020-06-05
The Elementor Page Builder plugin before 2.9.9 for WordPress suffers from multiple stored XSS vulnerabilities. An author user can create posts that result in stored XSS vulnerabilities, by using a crafted link in the custom URL or by applying custom attributes.
CVE-2020-11696
PUBLISHED: 2020-06-05
In Combodo iTop a menu shortcut name can be exploited with a stored XSS payload. This is fixed in all iTop packages (community, essential, professional) in version 2.7.0 and iTop essential and iTop professional in version 2.6.4.
CVE-2020-11697
PUBLISHED: 2020-06-05
In Combodo iTop, dashboard ids can be exploited with a reflective XSS payload. This is fixed in all iTop packages (community, essential, professional) for version 2.7.0 and in iTop essential and iTop professional packages for version 2.6.4.
CVE-2020-13646
PUBLISHED: 2020-06-05
In the cheetah free wifi 5.1 driver file liebaonat.sys, local users are allowed to cause a denial of service (BSOD) or other unknown impact due to failure to verify the value of a specific IOCTL.