DS Unit 3 Part Two
DS Unit 3 Part Two
Access Control is a way of granting or denying access to a set of information or resources. The
exponential increase in data generation and maintenance has also brought unique challenges and
requirements for stringent privacy protection and security. Advances in networking and cloud
computing have increased collaboration between multiple users. As a result, this also makes
networks and systems vulnerable to the threat of attacks and data leaks. Data access to unwanted
entities can cause data security issues, monetary losses, and raises impending privacy concerns
for the organizations. Imposing access control has become a crucial part of data and information
security for these reasons.
Why Access Control is important and useful:
Access Control requires user identification and authentication to ensure it belongs to the
permitted set of users to request access. Access Control grants or limits user access to resources.
Access Control can assess user access patterns to identify malicious bots and deny access to help
protect data privacy. Bots are often used to mimic human behavior and can perform automated
and sometimes harmful, tasks.
Anomalous user access behavior often indicates suspicious network activity. Access Control can
aid in the timely detection of security threats and prevent them.
Access Control helps detect anomalous user activity and helps safeguard systems from intrusion
and security breaches.
Restricting users that should not be accessing the information and resources keeps data
confidential, protected, and less prone to leakage.
Access Control is commonly formulated for two conceptual entities: Subjects and Objects.
Elements of Access Control
Access control policies are high-level requirements that specify how access is managed and who
may access information under what circumstances. International Organization for
Standardization (ISO) defines security standards that organizations must comply with to ensure
and execute data privacy and security. Access Control Lists implement these policies for a
system or network resource component.
Access Control Models provide a defined structure to implement access control policies.
Organizations can choose to implement one or a combination of the access control models based
on the custom security requirements and existing infrastructure.
The following are some of the common types of access control models:
Discretionary Access Control (DAC): The data owner decides the users’ selection and the
permissions to be granted to users that access the data.
Access control of this type is simple to implement and maintain. Users get more
autonomy over the changes if they have access rights.
Such approaches might run into conflicting user permissions and might not be as
secure as other approaches.
Mandatory Access Control (MAC): Organization’s administrator sets strict policies on
individual users and/or the data, resources, and information accessed by the users. Users cannot
add, alter, or remove any permissions.
Such models can be used when central access policies are enforced, and it is easier
to compartmentalize resource access to a subset of users.
However, this model might not be a requirement for an organization that depends
highly on collaboration and lacks management resources to implement the model.
Role-Based Access Control (RBAC): The system administrator decides the level of priority or
access given to users based on their role in the organization. The assigned permissions allow the
user limited access to resources or limited permissions to information. The users can perform
actions or access information based on the level of visibility granted by the RBAC.
This approach is very flexible and makes it easy to maintain user access for well-
defined organizational hierarchies.
The role and responsibility assigned to the users can pose a risk to overprivileged
users due to the complexity of the access assignment.
Attribute-based Access Control (ABAC): This is a context-based dynamic policy. The access
control is based on policies assigned to the users.
Being attribute-based and dynamic, this approach is more targeted, robust, and
scalable.
The implementation process is quite complicated and time-consuming.
Break-glass Access Control: Generally implemented in case of emergency, a user generally not
authorized is given access or allowed to create a new account which would not be permitted in
normal conditions.
This approach can help prevent threats or mitigate damages in case of a security
emergency.
Generally, this is used in emergencies and is not too secure or meant to be used for
long-term needs.
Rule-based Access Control: System Admin defines certain condition-based rules limiting
company resource access.
Absolute: Define a particular date and time or time range when access is granted or
prohibited to a set of certain users.
Periodic: Define access control for a certain time range that repeats after a certain period.
Firewall settings can define the temporal access control of a network and network devices for a
user or set of users. Permissions can be set and altered accordingly.
Based on Figure 1 above, the following are some scenarios/examples of time-based access
control;
The confinement problem deals with preventing a process from taking disallowed actions.
Consider a client/server situation: the client sends a data request to the server; the server uses the
data, performs some function, and sends the results (data) back to the client. In this case the
confinement problem deals with preventing a server from leaking information that the user of
that service considers confidential.
Goal of service provider 1. The server must ensure that the resources it accesses on behalf of the
client include only those resources that the client is authorized to access.
Goal of the service user 2. The server must ensure that it does not reveal the client’s data to any
other entity not authorized to see the client’s data.
Def: The confinement problem is the problem of preventing a server from leaking information
that the user of the service considers confidential.
Observations
This implies that the process cannot do any computations because an analyst could
observe the flow of control and deduce information about the inputs.
A process that cannot be observed and cannot communicate with other processes cannot
leak information. This is called total isolation.
CPU
networks disk
storage
unconfined processes can transmit information over shared resources How might a process do
this?
Def: A covert channel is a path of communication that was not designed to be used for
communication
e.g. process p is confined and cannot communicate with q p & q share a file system both have
read, create, delete privilege to the same directory
continue the process above until p creates a file called end when q knows that the message is
sent.
Def: The rule of transitive confinement states that if a confined process invokes a second
process, the second process must be as confined as the caller.
Confinement is a mechanism for enforcing the principle of least privilege. The problem is that
the confined process needs to transmit data to another process. The confinement needs to be on
the transmission, not on the data access. The confinement mechanism must distinguish between
transmission of authorized data and the transmission of unauthorized data. This presents a
dilemma in that modern computers are designed to share resources and yet by the act of sharing
they create channels of communications along which information can be leaked.
e.g. One process can read the time by checking the system clock or counting the number of
instructions executed.
A second process can write the time by executing a set number of instructions and stopping