LEcture 4
LEcture 4
k
ee
W
CS 3923/CS 6813
Computer Security/Information
Security & Privacy
Security Policies
Security Policy
● A security policy is a set of rules stating which actions are
permitted and which are not.
● Can be informal or highly mathematical.
● If we consider a computer system to be a finite state
automaton with state transitions, then
○ A security policy is a statement that partitions the states of a system
into a set of authorized or secure states and a set of unauthorized or
non-secure states.
○ A secure system is a system that starts in an authorized state and
cannot enter an unauthorized state.
○ A breach of security occurs when a system enters an unauthorized
state.
● We expect a trusted system to enforce the required security
policies.
4
k
ee
W
Definitions
● There is no standard definition of security policy.
● Some define them as documents for humans to read:
○ The SANS Institute defines a security policy as "a document that
outlines specific requirements or rules that must be met...usually
point-specific, covering a single area.”
○ SearchSecurity.com: "In business, a security policy is a document that
states in writing how a company plans to protect the company's
physical and information technology (IT) assets.”
○ ISO17799: “To provide management direction and support for
information security”
4
k
ee
W
Definitions (continued)
● But in other contexts, machine readable instructions are also
called policy:
○ The term “firewall policy” is typically used for the firewall rule set
○ Crypto policy (acceptable algorithms, key lengths) are used in IPSec
Security Association (SA) negotiations
○ Machine readable policies all derive from text-based policies, and
should just be machine readable versions of human readable policies
(possibly with detail added)
● Many documents about policy focus on policies for users and
employees (e. g., acceptable use policies)
● We take a broad view of what a policy is, but focus on
“human readable policies”
4
k
ee
W
Mechanism or Policy?
4
k
ee
W
Mechanism or Policy?
4
k
ee
W
Security Models
● To formulate a security policy you have to describe
entities it governs and what rules constitute it – a
security model does just that!
● A security model is a model that represents a
particular policy or set of policies. They are used
to:
○ Describe or document a policy
○ Test a policy for completeness and consistency
○ Help conceptualize and design an implementation
○ Check whether an implementation meets requirements.
4
k
ee
W
Example
Top Secret (TS) Dean Jelena Strategic Files
| | |
Secret (S) Prof. Gerig Personnel Files
| | |
Confidential (C) Susana Student Files
| | |
Unclassified (UC) Prof. Cappos Class Files
A basic confidentiality classification system. The four levels are arranged on the
list from most sensitive at top and least sensitive at bottom. In the middle are
individuals grouped by their security clearance and at the right are documents
grouped by their security level.
So Prof. Cappos can read class files and Dean Jelena can read any file. But
what if Dean Jelena reads contents of personnel files and writes them onto the
CS392 class file?
4
k
ee
W
Lower Level
● If Alice wants to talk to Bob who is at a lower level
how does she write a message to him?
● BLP allows this by having notion of maximum-security
level and current security level.
● Maximum security level must dominate current
security level.
● A "trusted subject" may effectively decrease its
security level
○ This effectively ignores the *-Property
4
k
ee
W
Tranquility Principle
● Recall: BLP assumed that security levels of objects are
constant.
● Principle of tranquility states that subjects and objects may
not change their security level once instantiated.
● Principle of strong tranquility states that security levels do
not change during the lifetime of the system.
● Principle of weak tranquility states that security levels do
not change in a way that violates the rules of a given
security policy.
4 What about other properties?
k
ee
W
Examples:
Doctor access to health records
Policy
● Policy for health information systems (Anderson).
● A patient is the subject of medical records, or an
agent for that person who can give consent for the
person to be treated.
● Protected Health Information is information about a
patient’s health or treatment enabling that patient to
be identified.
● A clinician is a healthcare professional who has
access personal access to personal health
information while performing their jobs.
4
k
ee
W
Access Principles
● Each medical record has an access control list naming the
individuals or groups who may read and append information to
the record. The system must restrict access to those identified
in the list.
● One of the clinicians on the access control list (responsible
clinician) must have the right to add other clinicians to the
access control list.
● The responsible clinician must notify the patient of the names
on the access control list whenever the patient’s medical record
is opened. Except for situations given in Statutes or in cases of
emergency the responsible clinician must obtain the patient’s
consent.
4
k
ee
W
Availability
4
k
ee
W
Non-repudiation
4
k
ee
W
Access Control
4
k
ee
W
Non-repudiation, Accountability
4
k
ee
W
Availability, Non-repudiation
4
k
ee
W
Access Control
4
k
ee
W
Confidentiality, Privacy
4
k
ee
W
Confidentiality
k
ee
4 What is the Basis for Most Security
W
Policies?
● Broader organizational, corporate or government policies
● Risk analysis:
○ Often qualitative (even intuitive) analysis
○ Usually only based on analysis of assets at risk and threats
■ Sensitivity of data (both confidentiality and integrity) is a major
source for many organizational level policies, which are based
on classes of information (e. g., secret, proprietary, SSN,
personal medical, etc.)
○ Vulnerabilities may drive lower level policy
● Concerns about image (corporate, agency, personal)
4
k
ee
W
Policies
4 Who Should Be Concerned About
k
ee
W
Security Policy
● Managers
● System designers
● Users: what are the policy’s impacts on their actions,
and what are the ramifications of not following policy
● System administrators, support personnel who
manage enforcement technologies and processes
● Company lawyers: they may have to use the written
policies in support of actions taken against
employees in violation
4
k
ee
W
(continued)
● Inclusive policies provide automatic prohibition for new
applications, technologies, (some) attacks, etc. without changing
policy
○ Downloading copyright material for personal use
○ Instant Messaging
● Inclusive policies may need to be updated and updates
distributed whenever a new application, technology, etc. comes
along
● It is a matter of (high level) corporate policy whether to use
inclusive or exclusive policies
4
k
ee
W
Management
● Configuration Management
● Ongoing Security Monitoring
● Security Patch Management
● Incident Response
● Business Continuity
● Security Audit
4
k
ee
W
(continued)
● Multiple levels of a policy may be in a single document, but
the development of the complete policy is “top down”
● This refinement process level policies may be integrated into
the system design process
○ For example, you cannot define a firewall policy until you know your
system will use a firewall as enforcement mechanism for a higher-level
policy
● “High level” and “lower level” policy is not a standard
terminology--this is a useful just a way to think about policies
● Some authors only consider the high-level policies as
“policies”
4
k
ee
W
PCI Policies
● Top Level: Credit card information should not be disclosed
○ Mid level: All PCI networks and systems will be protected against “snooping”
by unauthorized entities
○ The PCI system shall not permit clerks or other customers to see PIN
numbers as they are entered by customers
● Top Level: The PCI system shall not violate the integrity of the authorization
process
○ Mid Level: Clerks shall not override a “no” response to a credit authorization
request
■ Lower Level: The PCI system shall automatically block completion of a
transaction that has been denied
(or)
■ Clerk shall be trained to never complete a transaction that has been
denied
(In practice policies would be more detailed and have more elements)
4
k
ee
W
Meet Cortana
4
k
ee
W
Yes.
Is this reasonable?
4
k
ee
W
No.
Yes.
Is this reasonable?
4
k
ee
W
Yes.
Is this reasonable?
4 Has Microsoft Gone Too Far?
k
ee
W
4 How Much Privacy Can You Really
k
ee
W
Have?
4
k
ee
W
A General Question
● Given a computer system, how can we determine if
it is secure? More simply, is there a generic
algorithm that allows us to determine whether a
computer system is secure?
● What policy shall define “secure?” For a general
result, the definition should be as broad as possible
– access control matrix with some basic operations
and commands.
4 Exam 1
k
ee
W
Seattle tutorials:
https://seattle.poly.edu/wiki/PythonVsRepy
https://seattle.poly.edu/wiki/RepyTutorial
https://github.com/SeattleTestbed/docs/tree/master/Und
erstandingSeattle
4 Reading Next Week
k
ee
W
Read: http://www.rcmp-grc.gc.ca/ts-st/pubs/phys-sec/g1-025-eng.htm
Ethics
Mechanism vs policy