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.

Operations

4/20/2016
11:00 AM
Jeff Schilling
Jeff Schilling
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

Internal Pen-Testing: Not Just For Compliance Audits Anymore

How turning your internal penetration team into a 'Friendly Network Force' can identify and shut down the cracks in your security program.

When evaluating or building a security operations program, one of my first steps is to ensure that a Friendly Network Forces (FNF) function is in place. I wish I could take credit for creating this concept. Readers with US Department of Defense backgrounds will recognize the nomenclature, commonly referred to as FNF or Blue Teams.  

What is FNF?

For most non-technical audiences, I describe FNF as internal penetration teams, but they do so much more. A sound FNF team will:

  • Search for gaps and seams through both internal and external penetration testing
  • Provide surveillance on critical portions of an enterprise that sophisticated threat actors will try to leverage 
  •  “Shake the door knobs” on security controls and devices to ensure they are working as they should (e.g. are those access controls really in place between segmented VLANs?)
  • Conduct proofs-of-concept (POCs) on zero-day or globally known vulnerabilities to see if an environment is vulnerable
  • Conduct insider threat surveillance

To truly gain the most of out these roles, it’s vital to look for certain attributes and skillsets.

For me, it is really simple. Team members must have extensive knowledge of how an enterprise environment is designed and possess a strong understanding of the most critical gaps and vulnerabilities. In fact, one of Armor’s FNF team members is one of our first employees, so he is someone who has a long history with the environment and understands each any every dark corner. It’s that important.

Understanding Threat Actors

FNF professionals should have the experience and contextual understanding of how real cyber threat actors target and attack their victims. There are great courses — the SANS-certified Network Penetration & Ethical Hacker course comes to mind — that provide solid foundations for this knowledge base. 

However, experience in leveraging this knowledge to penetrate networks is a difficult skill for potential FNF team members to acquire. Normally, you can’t apply this knowledge without facing legal or ethical ramifications.

That’s why alumni from national-level intelligence agencies or security consultants, who have worked as both close and remote access penetration testers, make great resources as do former incident response and forensics investigators.

Strong Moral Compass

Members of the team must be of high moral character. This might sound corny and obvious to some, but it is very important that members of the FNF team are very discreet in their activities and can be trusted with the highest levels of access within an organization. 

These teams watch everyone. They look for any and all anomalous activity — from the front-desk admin to the greater security team to the CSO. It’s even a good idea to include them on HR situations where an employee could be an insider threat. 

I am confident that if my FNF discovered that my laptop was compromised, they would have the authority and moral courage to let me and the CEO know that I screwed up. That is the litmus test for every member of our FNF team. This type of character and visibility should be present in every organization.  

More Than ‘Testers’

FNF teams are more than just internal pen-testers. When employed correctly, they will identify and shut down the cracks and seams in your security program. They will validate that your security operations team is doing what they say they are doing. And they will lock in on any unscrupulous, suspicious or erratic behavior within your organization.

I can’t imagine a mature security organization NOT having an FNF team. That is, unless they are afraid to know the truth. But as high-profile breaches have proven, this strategic ignorance will not prevent consequences. It only exacerbates them.

Gain insight into the latest threats and emerging best practices for managing them. Attend the Security Track at Interop Las Vegas, May 2-6. Register now!

Jeff Schilling, a retired U.S. Army colonel, is Armor's chief security officer. He is responsible for the cyber and physical security programs for the corporate environment and customer-focused capabilities. His areas of responsibilities include security operation, governance ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: -when I told you that our cyber-defense was from another age
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
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-2011-3349
PUBLISHED: 2019-11-19
lightdm before 0.9.6 writes in .dmrc and Xauthority files using root permissions while the files are in user controlled folders. A local user can overwrite root-owned files via a symlink, which can allow possible privilege escalation.
CVE-2019-10080
PUBLISHED: 2019-11-19
The XMLFileLookupService in NiFi versions 1.3.0 to 1.9.2 allowed trusted users to inadvertently configure a potentially malicious XML file. The XML file has the ability to make external calls to services (via XXE) and reveal information such as the versions of Java, Jersey, and Apache that the NiFI ...
CVE-2019-10083
PUBLISHED: 2019-11-19
When updating a Process Group via the API in NiFi versions 1.3.0 to 1.9.2, the response to the request includes all of its contents (at the top most level, not recursively). The response included details about processors and controller services which the user may not have had read access to.
CVE-2019-12421
PUBLISHED: 2019-11-19
When using an authentication mechanism other than PKI, when the user clicks Log Out in NiFi versions 1.0.0 to 1.9.2, NiFi invalidates the authentication token on the client side but not on the server side. This permits the user's client-side token to be used for up to 12 hours after logging out to m...
CVE-2019-19126
PUBLISHED: 2019-11-19
On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR ...