SLIDE 1 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 1
U C U C D A VI S MATT BISHOP SOPHIE ENGLE SEAN PEISERT SEAN WHALEN CA LABS CARRIE GATES LAKE TAHOE, CA NSPW W 09.23. .23.2008 2008
WE HAVE MET THE ENEMY AND HE IS US
SLIDE 2 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 2
WHAT WE SHOW How to define and analyze the insider problem WHAT WE DON’T SHOW How to detect, deter, mitigate,
- r solve the insider problem
WHY IT’S IMPORTANT Identifies highest-risk resources and highest-threat insiders WHAT WE SAW Binary, perimeter-based definition
- f insiders hinder threat analysis
SLIDE 3 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 3
NAVIGATION
Main Sections:
- Part 1: Unifying Policy Hierarchy
- Part 2: Existing Insider Definitions
- Part 3: Attribute-Based Group Access Control
Supplemental:
SLIDE 4
PART 1
Understanding Insiders and Insider Threat
SLIDE 5 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 5
CLAIMS
- The complexity of security policy is key to
understanding the insider problem.
- Binary or perimeter-based definitions of an
insider impede threat analysis.
- The ABGAC model identifies “insiderness”
with respect to a resource and allows for insider threat analysis.
SLIDE 6
SECURITY POLICY
The Complexities
SLIDE 7 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 7
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
SLIDE 8 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 8
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Ideal Policy:
- Yasmin is authorized to read {} records for the
purpose of treating {} patients.
- Yasmin is authorized to append {} records for the
purpose of treating {} patients.
Feasible?
SLIDE 9 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 9
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Ideal Policy:
- Yasmin is authorized to authenticate as yasmin.
- yasmin is authorized to read {} records.
- yasmin is authorized to append {} records.
SLIDE 10 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 10
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Ideal Policy:
- Yasmin is authorized to authenticate as yasmin.
- yasmin is authorized to read {} records.
- yasmin is authorized to append {} records.
Practical?
SLIDE 11 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 11
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Ideal Policy:
- Yasmin is authorized to authenticate as yasmin.
- yasmin is authorized to read all records.
- yasmin is authorized to write all records.
Possible?
SLIDE 12 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 12
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Ideal Policy:
- Yasmin is authorized to authenticate as yasmin.
- yasmin is authorized to read all records.
- yasmin is authorized to write all records.
- yasm
smin in can delete all records.
Exploit!
SLIDE 13 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 13
POLICY EXAMPLE
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
The Different Policies:
- What is ideal?
- What is feasible?
- What is practical?
- What is possible?
SLIDE 14
SECURITY POLICY
The Unifying Policy Hierarchy
SLIDE 15 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 15
UNIFYING POLICY HIERARCHY
What is the Unifying Policy Hierarchy?
- Introduced by Carlson in 2006:
- Carslon, Adam, “The Unifying Policy Hierarchy Model,”
Master’s Thesis, UC Davis, June 2006.
- A hierarchical model of security policy at different
levels of abstraction.
What is it good for?
- Analyzing gaps in the hierarchy lead to insight to
where and why problems occur
SLIDE 16 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 16
EXAMPLE SCENARIO
The Scenario:
- Yasmin, a doctor, is only authorized to read and
append medical records of her patients for the purpose of treating them.
SLIDE 17 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 17
EXAMPLE SCENARIO
Oracle Policy (Ideal)
OP( subject, object, action, environment/intent ) = { authorized, unauthorized } OP(s,o,a,e) = authorized
- Yasmin, yasmin, authenticate, any
- yasmin, {} records, read, treating {} patients
- yasmin, {} records, append, treating {} patients
SLIDE 18 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 18
EXAMPLE SCENARIO
Feasible Policy (Feasible)
FP( subject, object, action ) = { authorized, unauthorized, unknown }
- FP( yasmin, {} records, read ) = authorized
- FP( yasmin, {} records, append ) = authorized
- FP( Yasmin, yasmin, authenticate ) = unknown
- FP( Xander, yasmin, authenticate ) = unknown
SLIDE 19 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 19
EXAMPLE SCENARIO
Configured Policy (≈Practical)
CP( subject, object, action ) = { authorized, unauthorized, unknown }
- FP( yasmin, {} records, read ) = authorized
- FP( yasmin, {} records, append ) = authorized
- CP( yasmin, all records, read ) = authorized
- CP( yasmin, all records, write ) = authorized
SLIDE 20 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 20
EXAMPLE SCENARIO
Real-Time Policy (Possible)
RP( subject, object, action ) = { possible, impossible }
- OP( Xander, yasmin, authenticate ) = unauthorized
- CP( yasmin, all records, delete ) = unauthorized
- RP( Xander, yasmin, authenticate ) = possible
- RP( yasmin, all records, delete ) = possible
SLIDE 21 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 21
POLICY GAPS
Oracle/Feasible Gap
Ex: user versus user account, user intent
Feasible/Configured Gap
Ex: slow removal of terminated employees
Configured/Real-Time Gap
- Implementation Errors and Vulnerabilities
Ex: buffer overflow, runtime vulnerability
SLIDE 22 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 22
POLICY GAPS
Action OP FP CP RP
Xander authenticates as xander.
? ?
xander accesses a website…
…to check the weather
? ?
…to expose system to exploit
? ?
Web browser leaks user password
Yasmin authenticates as xander.
? ?
SLIDE 23
UNIFYING POLICY HIERARCHY
Understanding Insiders and Insider Threat
SLIDE 24 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 24
DEFINITIONS
Who are the Insiders?
- Anyone with more privileges in a lower level of policy
than at a higher level of policy.
What is the Insider Problem?
- Insiders have more permissions than necessary to
perform their jobs.
- Insiders must be trusted not to misuse these
permissions for other purposes.
SLIDE 25 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 25
PRIMITIVE INSIDER MISUSES
- Violate OP using privileges in CP or FP
- Ex: Misuse privileges for personal gain.
- Violate FP using privileges in CP
- Ex: Fired employee logs on and changes passwords.
- Violate CP using privileges in RP
- Ex: Exploit buffer overflow inside firewall perimeter to
increase privileges.
Assume FP = CP? “Legitimate” Access Misuse “Illegitimate” Access Misuse
SLIDE 26 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 26
EXAMPLE OF INSIDER MISUSE
Scenario:
Yasmin sells information from all medical records to insurance companies.
- Intent unauthorized in OP
- Intent unrecognized in FP
- Access to all records unauthorized in FP
- Access to all records authorized in CP
Potential for misuse!
SLIDE 27 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 27
INSIDERNESS
Definition:
- A “measure” of an insider’s potential for misuse
- Loosely based on “size of gaps” for an insider
Example:
- Programmer with read and commit access to svn for a
specific project
- System administrator for SVN with root access for all
company projects
SLIDE 28 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 28
WHAT DO WE LEARN?
There are different categories of insider misuse
- OP/CP Misuse (Legitimate Privilege Misuse)
- CP/RP Misuse (Illegitimate Privilege Misuse)
Insider misuse is not always linked to cyber access
- Some misuse occurs at higher levels of the hierarchy.
- Some misuse is the result of social or physical factors.
- The Insider Problem predates computers anyway!
SLIDE 29 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 29
WHAT DO WE LEARN?
Some insiders have higher degree of “insiderness”
- How big are the gaps?
- How much access does the insider have?
- How do we measure or capture “insiderness”?
We need to perform insider threat analysis!
SLIDE 30
PART 2
Existing Definitions of Insiders
SLIDE 31 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 31
CLAIMS
- The complexity of security policy is key to
understanding the insider problem.
- Binary or perimeter-based definitions of an
insider impede threat analysis.
- The ABGAC model identifies “insiderness”
with respect to a resource and allows for insider threat analysis.
SLIDE 32
EXISTING DEFINITIONS
SLIDE 33 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 33
Insider: Anyone operating inside the security perimeter.
(Patzakis, “New Incident Response Best Practices,” 2003.)
insiders
TOO SIMPLE
SLIDE 34 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 34
http://www.cenic.net/operations/documentation/CENIC-Design.jpg
Reality is more complex.
SLIDE 35 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 35
Someone with access, privileges, or knowledge
- f information systems and services.
(RAND, “Understanding the Threat,” 2004.)
INSIDER
Binary Classification
- Insider( Name ) = { Yes, No }
- Xander, has access and knowledge
- Yasmin, has just knowledge
- Insider( Xander ) = Insider( Yasmin ) = Yes
SLIDE 36 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 36
Someone with access, privileges, or knowledge
- f information systems and services.
(RAND, “Understanding the Threat,” 2004.)
INSIDER
What type of access?
- Cyber only?
- Saw how other types of access lead to insider
problems in the policy hierarchy
SLIDE 37
OUR APPROACH
SLIDE 38 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 38
OUR APPROACH
Avoid perimeters
- Define an insider with respect to a resource
Avoid binary classification
- Assign “insiderness” based on level of access
Avoid cyber-only access
- Include physical, cyber, and social access
- Include subjects, objects, actions from Oracle Policy
SLIDE 39
PART 3
Identifying Insiders and Analyzing Insider Threat
SLIDE 40 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 40
CLAIMS
- The complexity of security policy is key to
understanding the insider problem.
- Binary or perimeter-based definitions of an
insider impede threat analysis.
- The ABGAC model identifies “insiderness”
with respect to a resource and allows for insider threat analysis.
SLIDE 41
ACCESS CONTROL
Identifying Insiders
SLIDE 42 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 42
USING RBAC
Definition:
- Role-Based Access Control
- Create roles based on job function
- Assign permissions to roles
- Assign roles to users
Usage:
- Identify all roles with access to resource
- Identify all users with those roles
SLIDE 43 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 43
RBAC SCENARIO
Attribute Name Job Function Building Access Server Access Wilma System Admin Before 5pm Both Xander Help Desk After 5pm Remote Yasmin Janitor Before 5pm Physical Zane Janitor After 5pm Physical
SLIDE 44 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 44
RBAC SCENARIO
Attribute Name Job Function Building Access Server Access Wilma System Admin Before 5pm Both Xander Help Desk After 5pm Remote Yasmin Janitor Before 5pm Physical Zane Janitor After 5pm Physical
Insiders With: Remote access to servers. RBAC Role: System Admin, Help Desk
SLIDE 45 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 45
RBAC SCENARIO
Attribute Name Job Function Building Access Server Access Wilma System Admin Before 5pm Both Xander Help Desk After 5pm Remote Yasmin Janitor Before 5pm Physical Zane Janitor After 5pm Physical
Insiders With: Physical access after 5pm RBAC Role: Janitor
SLIDE 46 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 46
RBAC SCENARIO
Attribute Name Job Function Building Access Server Access Wilma System Admin Before 5pm Both Xander Help Desk After 5pm Remote Yasmin Janitor Before 5pm Physical Zane Janitor After 5pm Physical
Insiders With: Physical access before 5pm RBAC Role: Unclear
SLIDE 47
ABGAC
Attribute-Based Group Access Control
SLIDE 48 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 48
INTRODUCING ABGAC
Attribute-Based Group Access Control
- Generalization of RBAC
- Assigns rights based on general attributes,
which may or may not include job function
- Inherits features of RBAC such as:
- “role containment” as “group containment”
- “separation of duty” becomes “conflicts of interest”
SLIDE 49 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 49
CONFLICTS OF INTEREST
Scenario:
- Xander, an executive at a company, is married to Yasmin.
- Xander has insider information that company stock will increase.
- There is a conflict of interest if Xander advises Yasmin to invest.
Groups:
- Group 1: Those given the insider information.
- Group 2: Those related to group 1.
Separation:
- Members of group 2 are forbidden to do anything forbidden to
members of group 1.
SLIDE 50
ABGAC
Building Blocks
SLIDE 51 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 51
RESOURCE PAIR
Definition:
A pair consisting of a resource (entity) and an access mode describing one way in which that entity can be accessed. ** Access mode not restricted to cyber access! The resource or access may come from any level in the policy hierarchy.
SLIDE 52 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 52
RESOURCE PAIR
Example:
(backups, erase) : ability to erase backup files Access includes anyone with:
- Privileges to delete files on the server
- Physical access to the hard drive
- Include what is possible (RP) not authorized (CP+)
SLIDE 53 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 53
RESOURCE DOMAIN
Definition:
A set of resource pairs. (similar to a protection domain, but includes physical, procedural, and cyber access and resource-oriented)
Example:
{ (backups, modify), (backups, erase) }
SLIDE 54 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 54
RD-GROUP
Definition:
A set of (one or more) resource domains. (can group domains required for multi-stage attacks,
- r domains with similar risk values)
Example:
{ { (backups, modify), (backups, erase) }, { (servers, login), (servers, configure) } }
SLIDE 55 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 55
USER GROUP
Definition:
The set of all subjects whose protection domains are a (possibly improper) superset of the associated rd-group. ** Protection domain is used broadly to include possible access from cyber, physical, and social domains.
SLIDE 56 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 56
ABGAC BUILDING BLOCKS
rd-group ( r, a ) ( r, a ) ( r, a ) ( r, a ) resource domains resource pairs users user group insider with respect to a resource
SLIDE 57
ANALYZING THREAT
A Simplified Example
SLIDE 58 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 58
ANALYZING THREAT
General Goals:
- Minimize impact of an insider attack
- Minimize number of known insiders
General Approach:
- Provide an ordering of resource domains
- Results in ordering of rd-groups
- Identify user groups for high-value rd-groups
- Users with highest value represent greatest risk
SLIDE 59
ANALYSIS EXAMPLE
The Scenario
SLIDE 60 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 60
ANALYSIS EXAMPLE
Scenario:
- Multinational company based in the US is developing
software for recording real-estate ownership over the Internet
Priorities:
- Preserve integrity and accountability
SLIDE 61 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 61
ANALYSIS EXAMPLE
Environment:
- Developers create and edit software on home
systems across the world
- Software is downloaded and uploaded over VPN
- Code resides on servers located in Iowa
- Server backed up daily by corporate office
SLIDE 62 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 62
ANALYSIS EXAMPLE
Resources:
- Developer Workstations (DWS)
- VPN Connection (VPN)
- Server (SVR)
- Backup Files (BAK)
Goal:
- Identify insiders that might insert trap doors
- Identify insiders that could debilitate company
- Destroy the code and its backups
SLIDE 63 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 63
ANALYSIS EXAMPLE
Worried About:
- Ability to alter code on DWS
(directly or indirectly)
- Ability to alter or destroy
code on SVR
- Ability to alter or destroy
code on BAK
transmission (mitm VPN)
RD-Groups:
- { ( DWS: login, tamper) }
- { ( SVR: write, destroy ) }
- { ( BAK: write, destroy ) }
- { ( VPN: configure ) }
SLIDE 64
ANALYSIS EXAMPLE
Identify User Groups
SLIDE 65 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 65
USER GROUPS: DETAILED
User Group: { ( DWS: login, tamper ) }
- Developers
- Anyone with physical access to the workstation
- Developers family
- Housekeepers
- Etc.
- Computer repair technicians
- Anyone with remote access to workstation
- Rogue websites
- Etc.
SLIDE 66 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 66
USER GROUPS: SIMPLIFIED
Actors:
- Vernon, a developer
- Wilma, Vernon’s nosey wife
- Xander, a system administrator
- Yasmin, president at corporate office
- Zane, janitor at corporate office
SLIDE 67 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 67
PROTECTION DOMAINS
DWS VPN SVR BAK log tamp config write dest write dest Vernon (developer)
Wilma (wife)
Xander (sysadmin)
Yasmin (president)
Zane (janitor)
SLIDE 68 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 68
PROTECTION DOMAINS
DWS VPN SVR BAK log tamp config write dest write dest Vernon (developer)
Wilma (wife)
Xander (sysadmin)
Yasmin (president)
Zane (janitor)
SLIDE 69
ANALYSIS EXAMPLE
Assign and Evaluate Metrics
SLIDE 70 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 70
VALUE RESOURCES
Assign metrics to rd-groups:
40 { (SVR: write, destroy), (BAK: write, destroy) } 24 { (SVR, destroy), (BAK, destroy) } 16 { (SVR, write), (BAK, write) } 8 { (SVR, write) } 2 { (DWS, tamper) }
SLIDE 71 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 71
VALUE RESOURCES
DWS VPN SVR BAK log tamp config write dest write dest Vernon: 18 (developer)
2 8 8
Wilma: 18 (wife)
2 8 8
Xander: 44 (sysadmin)
4 8 12 8 12
Yasmin: 20 (president)
8 12
Zane: 24 (janitor)
12 12
SLIDE 72 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 72
PROTECTION DOMAINS
DWS VPN SVR BAK log tamp config write dest write dest Vernon (developer)
Wilma (wife)
Xander (sysadmin)
Yasmin (president)
Zane (janitor)
SLIDE 73 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 73
VALUE ACCESS ATTRIBUTES
Assign metric to attribute groups:
4 upper management access 3 system administrator access 2 developer access 1 other staff access
SLIDE 74 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 74
EVALUATE METRICS
Name( user metric, resource metric )
V( 2, 18 ) V( 2, 18 ) Y( 4, 20 ) Y( 4, 20 ) W( 2, 18 ) W( 2, 18 ) X( 3, 44 ) X( 3, 44 ) Z( 1, 24 ) Z( 1, 24 )
SLIDE 75
ANALYSIS EXAMPLE
Reality Check
SLIDE 76 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 76
REALITY CHECK
- Simplified Scenario
- Simplified resources
- Simplified user groups
- Simplified metrics
- The Reality
- Difficult to anticipate avenues of attack
- Cost functions difficult to create
- Analysis possible for high-value resources and high-
risk insiders?
SLIDE 77
CLAIMS
A Review
SLIDE 78 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 78
CLAIMS
- The complexity of security policy is key to
understanding the insider problem.
- Binary or perimeter-based definitions of an
insider impede threat analysis.
- The ABGAC model identifies “insiderness”
with respect to a resource and allows for insider threat analysis.
SLIDE 79 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 79
QUESTIONS?
SLIDE 80 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 80
U C U C D A VI S MATT BISHOP SOPHIE ENGLE SEAN PEISERT SEAN WHALEN CA LABS CARRIE GATES LAKE TAHOE, CA NSPW W 09.23. .23.2008 2008
WE HAVE MET THE ENEMY AND HE IS US
SLIDE 81
SUPPLEMENTAL
Definitions
SLIDE 82 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 82
INDEX
Attribute-Based Access Control Configured Policy Feasible Policy Illegitimate Access Misuse Insider Insider Problem Insiderness Legitimate Access Misuse Oracle Policy Protection Domain RD-Group Real-Time Policy Resource Domain Resource Group Role-Based Access Control Unifying Policy Hierarchy User Group
SLIDE 83 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 83
INSIDER
Anyone with more privileges in a lower level of policy than at a higher level of policy.
SLIDE 84 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 84
INSIDER PROBLEM
Insiders have more permissions than necessary to perform their jobs. Insiders must be trusted not to misuse these permissions for other purposes.
SLIDE 85 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 85
INSIDERNESS
A “measure” of an insider’s potential for misuse.
SLIDE 86 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 86
UNIFYING POLICY HIERARCHY
A hierarchical model of security policy at different levels of abstraction, introduced by Adam Carlson in his Master’s Thesis.
SLIDE 87 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 87
ORACLE POLICY
Ideal policy, even if not explicitly defined. OP( subject, object, action, environment/intent ) = { authorized, unauthorized }
SLIDE 88 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 88
FEASIBLE POLICY
Attempts to approximate the Oracle Policy while taking into account the limitations of policy
- technology. Only able to understand system-
definable subjects, objects, and actions, and returns unknown for anything outside its domain. FP( subject, object, action ) = { authorized, unauthorized, unknown }
SLIDE 89 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 89
CONFIGURED POLICY
Policy as configured on the system. CP( subject, object, action ) = { authorized, unauthorized, unknown }
SLIDE 90 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 90
REAL-TIME POLICY
Reflects what is possible on the system. RP( subject, object, action ) = { possible, impossible }
SLIDE 91 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 91
LEGITIMATE ACCESS MISUSE
Violating Oracle Policy using access granted in Feasible Policy or Configured Policy.
SLIDE 92 WE HAVE MET THE ENEMY AND HE IS US MATT BISHOP ∙ SOPHIE ENGLE ∙ CARRIE GATES ∙ SEAN PEISERT ∙ SEAN WHALEN NEW SECURITY PARADIGMS WORKSHOP SEPTEMBER 23 2008 ∙ LAKE TAHOE, CA ∙ SLIDE 92
ILLEGITIMATE ACCESS MISUSE
Violating Configured Policy using access granted in the Real-Time Policy.