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.

Endpoint

5/13/2013
12:52 PM
Tim Rohrbaugh
Tim Rohrbaugh
Commentary
50%
50%

Use A Human Trust Model For Endpoints

Use anthropomorphic references to engage your brain and strengthen your approach to security

Have you ever used a feminine pronoun when talking about a boat? What about a computer program? Have you ever resented your computer after you felt it "intended" to lose your work? (I will refrain from linking to a YouTube video showing someone beating their office computer.)

People endowing inanimate objects with human characteristics is commonplace today. I believe it's also a useful approach when dealing with security design, controls, and analysis. Just as analogies and metaphors aid in helping the brain process new information, thinking of your endpoints as having human intentions (regardless of whether a real one is there at the moment) is also a very useful aid because it engages the two ancient almond-shaped regions of your brain called the amygdala.

She trusts me, she trusts me not, she ...

One type of the human trust model takes three forms: Trust no one at any time, trust some of the people some of the time, and trust all of the people all of the time. It is best when designing your network to match up devices, applications, and people based on this trust model. Why? So you can focus your efforts in the most effective way when defining controls, processing logs, and correlating events. By "effective" I mean likely to increase your security posture.

Do you trust everyone and everything the same?

How about the computers used by your road warriors? What about the systems exposed to the Internet? How about security software? Vendor-hosted systems? No, you don't trust all of these the same. You create zones of trust. You and everyone around you, regardless of their job roles, are experts at risk analysis. Why? Because they have survived walking across busy streets. Now all you need to do is apply these evolved senses to modern-day technology challenges by training your brain and linking human traits to those that live on your network.

How does it work?

Start with a pattern like this:

  • Trust no one at any time (I don't trust you) = trust 3
  • Trust some of the people some of the time (I trust you, but will verify) = trust 2
  • Trust all of the people all of the time (I trust you) = trust 1

Note: There is a trust 0 (something akin to subconscious) and trust 4 (enemy) AND the higher trust number = less trust

Next:

Place trust # entities together; when they're mismatched over time, classify/reclassify them as the highest trust number between them. Focus your controls, log capture, and analysis on those you do not trust, then verify those you do trust with the leftover team hours.

Sample: You see traffic coming from these examples ... How will you trust them?

  • Web server in a demilitarized zone (DMZ) [trust 3] uses standalone accounts or ones that have no privileges [trust 3] in inner layers
  • Development workstation in development area [trust 2] with users who are not admins, but developers [trust 2]
  • Production database server with no outside access [trust 1] with no interactive users (no one logged on) [trust 1]

Have kings been toppled by their inner circle? Sure they have. But did those in the inner circle responsible commingle with the untrusted at some point? Did they transition to the inner circle through other levels of trust? Yes, they did. Do you feel like arguing this point, linking your argument to an historical event, and/or taking this approach (called profiling) personally? Then you get my point. It's hard to be passionate and accurate when dealing with, "IP address: X connecting to Y with a byte count of X." So engage your amygdala by endowing endpoints with the expectation of trust ... as you do people.

Tim Rohrbaugh VP. Information Security for Intersections Inc. Tim Rohrbaugh is an information security practitioner who used military (comsec) experience to transition, in the mid 90's, to supporting Government Information Assurance (IA) projects. While splitting time between penetration testing and teaching at DISA, Mr. Rohrbaugh ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
MITRE Releases 2019 List of Top 25 Software Weaknesses
Kelly Sheridan, Staff Editor, Dark Reading,  9/17/2019
Preventing PTSD and Burnout for Cybersecurity Professionals
Craig Hinkley, CEO, WhiteHat Security,  9/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14821
PUBLISHED: 2019-09-19
An out-of-bounds access issue was found in the Linux kernel, all versions through 5.3, in the way Linux kernel's KVM hypervisor implements the Coalesced MMIO write operation. It operates on an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write indices 'ring->first' and 'ring->l...
CVE-2019-15032
PUBLISHED: 2019-09-19
Pydio 6.0.8 mishandles error reporting when a directory allows unauthenticated uploads, and the remote-upload option is used with the http://localhost:22 URL. The attacker can obtain sensitive information such as the name of the user who created that directory and other internal server information.
CVE-2019-15033
PUBLISHED: 2019-09-19
Pydio 6.0.8 allows Authenticated SSRF during a Remote Link Feature download. An attacker can specify an intranet address in the file parameter to index.php, when sending a file to a remote server, as demonstrated by the file=http%3A%2F%2F192.168.1.2 substring.
CVE-2019-16412
PUBLISHED: 2019-09-19
In goform/setSysTools on Tenda N301 wireless routers, attackers can trigger a device crash via a zero wanMTU value. (Prohibition of this zero value is only enforced within the GUI.)
CVE-2019-16510
PUBLISHED: 2019-09-19
libIEC61850 through 1.3.3 has a use-after-free in MmsServer_waitReady in mms/iso_mms/server/mms_server.c, as demonstrated by server_example_goose.