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.

Vulnerabilities / Threats

4/29/2019
04:00 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

7 Types of Experiences Every Security Pro Should Have

As the saying goes, experience is the best teacher. It'll also make you a better and more well-rounded security pro.
Previous
1 of 8
Next

Image Source: Adobe Stock: lassedesignen

Image Source: Adobe Stock: lassedesignen

Whether it's a military network, an e-commerce site, or a nonprofit group, organizations are constantly under attack — and they're looking to their security teams to protect them.

So what types of skills and experiences do security pros need to develop to succeed? Being good at technology is a given — that's why they went into the field in the first place. In talking to seven security pros, what came up time and again was that they need to be good listeners and develop communication and business skills.  

It's time for security pros to ask themselves what's really important to them and their organizations, says Paul Kurtz, co-founder and CEO of TruStar.

"It's not always about adding new tools," he says. "In fact, we went through a period after the Target and Anthem hacks and all the other major hacks where security pros were just overlaying tools on top of one another. A lot of those tools became shelfware."

Of course, that doesn't mean security pros should stop learning and build new skills. Yet another way to learn is through experiencing different situations on the job. Following are seven types of experiences that will make you a better and more well-rounded security pro, whether you're a one-person operation or work in a large SOC.

[Hear Paul Kurtz, co-founder and CEO of TruStar, present Cybersecurity Crash Course, Day 2 at Interop 2019 next month]

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
gmax28
100%
0%
gmax28,
User Rank: Strategist
5/10/2019 | 6:21:22 PM
Just not realistic...
The author is obviously not in the business of InfoSec.  Working in major enterprises for almost 20 years, you do your piece of the pie.  Rarely are there opportunities to learn other skills because your piece of the pie is quite large.  And shadowing an exec... yeah... ok.  Yes, InfoSec should understand the business aspects of IT just as much as the business should understand the importance of securing the environment.  

And to add to this, employers think that there are a plethora of experienced infosec guys out there and they make demands on "requirements" that just are not realistic.  Many times asking for what would equate to multiple jobs.  "Segregation of duties" anyone?  I had an HR person tell me that I was not considered because I performed the duties they were after more than 5 years ago.  Apparently they think that if you haven't done it lately, you clear your cache of any unused information.  I actually asked one HR person, " Did you forget how to ride a bike?"  She was stunned and didn't know how to answer that question. 

So this article is just another journalistic waste of time, and waste of my time perusing it.   Employers must consider a person's experience and allow some room for training/learning of new skills particular to their environment.  That's the only way you are going to get past a couple of skills unless you work for a very small company and are doing it all. 
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
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
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19782
PUBLISHED: 2019-12-13
The FTP client in AceaXe Plus 1.0 allows a buffer overflow via a long EHLO response from an FTP server.
CVE-2019-19777
PUBLISHED: 2019-12-13
stb_image.h (aka the stb image loader) 2.23, as used in libsixel and other products, has a heap-based buffer over-read in stbi__load_main.
CVE-2019-19778
PUBLISHED: 2019-12-13
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer over-read in the function load_sixel at loader.c.
CVE-2019-16777
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of pa...
CVE-2019-16775
PUBLISHED: 2019-12-13
Versions of the npm CLI prior to 6.13.3 are vulnerable to an Arbitrary File Write. It is possible for packages to create symlinks to files outside of thenode_modules folder through the bin field upon installation. A properly constructed entry in the package.json bin field would allow a package publi...