Operations

4/27/2015
10:30 AM
Marilyn Cohodas
Marilyn Cohodas
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
100%
0%

Twitter's Top 10 Social CISOs

If you work in information security today, you're on Twitter. Or are you?
Previous
1 of 11
Next

Wanted: CISO Tweeters
Who are the most socially-engaged chief information security officers? Researchers at the Boston security consulting firm  K logix wanted to find out, and offered to share their results with us. 

The research was based on a simple methodology starting with a search on Twitter for the title of CISO. Each CISO was given a score based on the number of followers, number of tweets, and ratio of number of followers to number of people they follow. The score for each of these categories was added together and then ranked to get the resulting list. We pared down the group to a Top 10 list but you can take a look at the  entire collection here. 
I'm sure there are many, many more social media-engaged CISOs who don't identify themselves via Twitter. So if you are one -- or have a recommendation for a colleague - please post the Twitter ID and related profile in the comments and we will keep a running list in order to expand the CISO Twittersphere.  

(Images: K logix)

Wanted: CISO Tweeters

Who are the most socially-engaged chief information security officers? Researchers at the Boston security consulting firm K logix wanted to find out, and offered to share their results with us.

The research was based on a simple methodology starting with a search on Twitter for the title of CISO. Each CISO was given a score based on the number of followers, number of tweets, and ratio of number of followers to number of people they follow. The score for each of these categories was added together and then ranked to get the resulting list. We pared down the group to a Top 10 list but you can take a look at the entire collection here.

Im sure there are many, many more social media-engaged CISOs who don't identify themselves via Twitter. So if you are one -- or have a recommendation for a colleague - please post the Twitter ID and related profile in the comments and we will keep a running list in order to expand the CISO Twittersphere.

(Images: K logix)

 

Marilyn has been covering technology for business, government, and consumer audiences for over 20 years. Prior to joining UBM, Marilyn worked for nine years as editorial director at TechTarget Inc., where she launched six Websites for IT managers and administrators supporting ... View Full Bio

Previous
1 of 11
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
5/11/2015 | 9:40:41 AM
University CISO
I was surprised to see a CISO in the University environment. I think it's great but is it common to see CISO's in education?
Want Your Daughter to Succeed in Cyber? Call Her John
John De Santis, CEO, HyTrust,  5/16/2018
New Mexico Man Sentenced on DDoS, Gun Charges
Dark Reading Staff 5/18/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-11354
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the IEEE 1905.1a dissector could crash. This was addressed in epan/dissectors/packet-ieee1905.c by making a certain correction to string handling.
CVE-2018-11355
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, the RTCP dissector could crash. This was addressed in epan/dissectors/packet-rtcp.c by avoiding a buffer overflow for packet status chunks.
CVE-2018-11356
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the DNS dissector could crash. This was addressed in epan/dissectors/packet-dns.c by avoiding a NULL pointer dereference for an empty name in an SRV record.
CVE-2018-11357
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the LTP dissector and other dissectors could consume excessive memory. This was addressed in epan/tvbuff.c by rejecting negative lengths.
CVE-2018-11358
PUBLISHED: 2018-05-22
In Wireshark 2.6.0, 2.4.0 to 2.4.6, and 2.2.0 to 2.2.14, the Q.931 dissector could crash. This was addressed in epan/dissectors/packet-q931.c by avoiding a use-after-free after a malformed packet prevented certain cleanup.