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.

Comments
New Security Mindset: Focus On The Interior
Newest First  |  Oldest First  |  Threaded View
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
5/8/2015 | 7:42:28 AM
Re: An Outline for a Quick and Dirty InfoSec Governance Team
@Christian, thanks for sharing this. A nice addition to Straight's insights. 
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
5/7/2015 | 5:15:37 PM
An Outline for a Quick and Dirty InfoSec Governance Team
This was a great interview and one of the most packed I've read in recent weeks with take-away material for research and reflection.  The notes on how focus on the wrong things for organizations when it comes to InfoSec rings true.  While not entirely focused on the "interior" I have a simplistic model below that does put focus on three key areas that ultimately translate to improving the integrity of "interior" data and processes.  

Not to oversimplify Information Security and the complex roles that need to be filled for organization-wide coverage, but these three points are great shortcuts to establishing an InfoSec governance team, especially for small orgs that may not have the resources for a formal loss prevention lifecycle.  Because the environment elements often overlap with these states, you then can have the same person (for very small teams) take more than one function.  

Org Function 1:

* Governs architecture/standards/implementation/lifecycle:  Network data that is in transit, flowing across internal networks and to the outside world (i.e., data on the wire and in the air). 

Org Function 2:

* Governs architecture/standards/implementation/lifecycle:  Data that is at rest on servers, databases, file shares, Intranet sites, workstations, laptops, mobile devices, portable storage, backup tapes, removable media, cloud storage. 

Org Function 3:

*  Governs usage standards/auditing/lifecycle:  Data that is in use in temporary memory on a local machine, an open report or running query on a workstation, an email that has been drafted but not sent, a file being copied to a USB drive, and data being copied and pasted from one local document to another. 

Feeding into all three of these areas would be incident response root cause analysis reports for continuous improvement for each lifecycle and their interfaces. 

A tight, compact approach to InfoSec and one that could improve upon some of the shortcomings this article mentions.

(Nod to Ernst & Young's 2011 data security report for some of the above verbiage.)
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/19/2015 | 3:06:13 PM
Re: Perimeter Emphasis

I agree. External and internal; security measures. Unless it is layered it does not really matter what you do in any side of your network perimeter.

Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/19/2015 | 3:03:51 PM
Re: Excellent interview of a person who has a clear understanding of information security. Thanks!

"You need to make sure Legal has a formal and well-defined role in IR before there's an incident"

I completely agree with this, at the end of the day, an incident would have a legal liability, you may want to cover that aspect of it from the beginning.

Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/19/2015 | 3:01:23 PM
Re: Excellent interview of a person who has a clear understanding of information security. Thanks!

I would not categorize humans as most sophisticated detection devices, they are sophisticated for sure and because of that could to really detect anything unless it is absolutely made visible to them. If we can take humans out of security equation we will be in better shape.

Dr.T
50%
50%
Dr.T,
User Rank: Ninja
3/19/2015 | 2:56:20 PM
An industry was created
I do not have an evidence to prove what I am saying here, there is a real industry is created on the security, security insurance, security devices and applications  companies are living their golden days. You can not create an industry by just hacking, there must be big investors and supports of this industry that we may not be aware of.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/19/2015 | 11:43:12 AM
Perimeter Emphasis
This was a great interview. I didin't realize how much emphasis was put on perimeter defenses and how underutilized internal defenses were until Jason alluded to this. Looking at it now, that fact couldn't have been more prevalent. I agree with his statements in the first step to moving towards increasing the security posture internally is to change the mind set of the human element with frequent human training sessions backed by the executives. Otherwise, we will continue to build these walls to the sky.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
3/19/2015 | 11:20:22 AM
Re: Excellent interview of a person who has a clear understanding of information security. Thanks!
Thank you for sharing your thoughts, @xmarksthespot. I think Straight's perspective as both a lawyer and a cyber security expert make his insights even more interesting and helpful.
xmarksthespot
50%
50%
xmarksthespot,
User Rank: Strategist
3/19/2015 | 2:50:30 AM
Excellent interview of a person who has a clear understanding of information security. Thanks!
Jason Straight has a clear understanding of core security principles. "I'm not saying forget the perimeter. It's got to be a balance, with a focus on the interior, too":  This is a well-crafted statement by Straight.  Defense-in-depth is a core security principle.

It appears he includes 2 factor authentication as part of internal security, but in my mind it also can be authentication via a site on the web, like some banks are now supporting, which is external.  It seems to me like the one other area internally is encryption of data at rest and data in transit (all internal network traffic). 

The human layer is definitely the most vulnerable, but I don't agree that is an intractable problem. ... Human beings are the most sophisticated detection devices you've got". - Another golden nugget from Mr. Straight. 

He has a good point where the security industry is pushing for people to purchase more and more endpoint solutions out there, and the focus should be internal controls.

Thank you, Jason Straight


Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Inside North Korea's Rapid Evolution to Cyber Superpower
Kelly Sheridan, Staff Editor, Dark Reading,  12/1/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Assessing Cybersecurity Risk in Todays Enterprises
Assessing Cybersecurity Risk in Todays Enterprises
COVID-19 has created a new IT paradigm in the enterprise and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25465
PUBLISHED: 2020-12-04
Null Pointer Dereference. in xObjectBindingFromExpression at moddable/xs/sources/xsSyntaxical.c:3419 in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25461
PUBLISHED: 2020-12-04
Invalid Memory Access in the fxProxyGetter function in moddable/xs/sources/xsProxy.c in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25462
PUBLISHED: 2020-12-04
Heap buffer overflow in the fxCheckArrowFunction function at moddable/xs/sources/xsSyntaxical.c:3562 in Moddable SDK before OS200903.
CVE-2020-25463
PUBLISHED: 2020-12-04
Invalid Memory Access in fxUTF8Decode at moddable/xs/sources/xsCommon.c:916 in Moddable SDK before OS200908 causes a denial of service (SEGV).
CVE-2020-25464
PUBLISHED: 2020-12-04
Heap buffer overflow at moddable/xs/sources/xsDebug.c in Moddable SDK before before 20200903. The top stack frame is only partially initialized because the stack overflowed while creating the frame. This leads to a crash in the code sending the stack frame to the debugger.