Chapter 4
Chapter 4
Access Control:
Access control is a security technique that regulates who or what can view or use resources
in a computing environment. It is a fundamental concept in security that minimizes risk to the
business or organization.
There are two types of access control: physical and logical. Physical access control limits
access to campuses, buildings, rooms and physical IT assets. Logical access control limits
connections to computer networks, system files and data.
To secure a facility, organizations use electronic access control systems that rely on user
credentials, access card readers, auditing and reports to track employee access to restricted
business locations and proprietary areas, such as data centers. Some of these systems
incorporate access control panels to restrict entry to rooms and buildings, as well as alarms
and lockdown capabilities, to prevent unauthorized access or operations.
Identification: For access control to be effective, it must provide some way to identify
an individual. The weakest identification capabilities will simply identify someone as
part of a vague, poorly defined group of users who should have access to the system.
Your username, a PGP e-mail signature, or even the key to the server closet provides
some form of identification.
Authentication: Identification requires authentication. This is the process of ensuring
that the identity in use is authentic — that it’s being used by the right person. In its
most common form in IT security, authentication involves validating a password linked
to a username. Other forms of authentication also exist, such as fingerprints,
smartcards, and encryption keys.
Authorization: The set of actions allowed to a particular identity makes up the meat
of authorization. On a computer, authorization typically takes the form of read, write,
and execution permissions tied to a username.
With a discretionary access control system (DAC) the owner of the company can decide how
many people have access to a specific location. Each access control point has a list of
DAC is defined as an access control policy enforced over all subjects and objects granting
information access that allows the subject to:
This is an access control method in which owners or administrators of the protected system,
data or resource set the policies defining who or what is authorized to access the resource.
Many of these systems enable administrators to limit the propagation of access rights. A
common criticism of DAC systems is a lack of centralized control.
DAC systems are considered to be the most flexible and offer the highest number of
allowances compared to other types of access control. Because it’s the most flexible, it’s also
not as secure as some other types, especially mandatory access control systems. Since one
person has total control over the system, he or she might grant access to someone who
shouldn’t have it. Discretionary access control systems are best for companies that expect the
most ease of use and flexibility.
Mandatory Access Control (MAC)
On the other end of the spectrum, mandatory access control systems (MAC) are the most
secure type of access control. Only owners and custodians have access to the systems. All the
access control settings are preset by the system administrator and can’t be changed or
removed without his or her permission.
This is a security model in which access rights are regulated by a central authority based on
multiple levels of security. Often used in government and military environments,
classifications are assigned to system resources and the operating system or security kernel.
MAC grants or denies access to resource objects based on the information security clearance
of the user or device. For example, Security-Enhanced Linux is an implementation of MAC on
Linux.
MAC as an access control policy uniformly enforced across all subjects and objects, ultimately
placing restrictions on DAC. MAC controls limit a subject’s access by preventing:
Role-based access control (RBAC) is quickly becoming the most popular type of access control.
Instead of assigning permissions to individual users like in a MAC system, an RBAC system
works by assigning permissions to a specific job title. It cuts down on the time required to set
up or change user access.
This is a widely used access control mechanism that restricts access to computer resources
based on individuals or groups with defined business functions -- e.g., executive level,
engineer level 1, etc. -- rather than the identities of individual users. The role-based security
model relies on a complex structure of role assignments, role authorizations and role
permissions developed using role engineering to regulate employee access to systems. RBAC
systems can be used to enforce MAC and DAC frameworks.
RBAC collects all the access permissions a user needs to complete their job function, both
explicitly outlined and implicitly needed, and maybe inherited through a hierarchy. A single
role may apply to one user or a group of users.
Under RBAC, you assign users access based on their job functions. Therefore, people in the
marketing department have access to the networks, systems, and applications they need to
do their jobs. This might include your customer relationship management (CRM) application,
corporate blog, social media accounts, folders that marketing uses in a shared drive, and your
collaboration tool. Additionally, not everyone on the marketing team will have the same
access to resources. Your social media manager may be the only person with access to those
accounts but does not have access to your corporate blog or CRM.
Additionally, you also need to remember that departments may need to have similar access
to resources for different reasons. Your sales team might need access to your CRM and some
of the same folders in a shared drive.
As the company’s application ecosystem grows, managing access becomes more challenging.
If your business closes at 5 p.m., there’s no need for anyone to have access to your main
office, even managers, after closing. With rule-based access control, you can set a rule to deny
access to everyone from 5 p.m. to 9 a.m. the next morning. Rules can be created for just about
any occasion.
Bell-LaPadula
Biba
Clarke Wilson Security Model
1. Bell-LaPadula
This Model was invented by Scientists David Elliot Bell and Leonard .J. LaPadula.Thus this
model is called the Bell-LaPadula Model. This is used to maintain the Confidentiality of
Security. Here, the classification of Subjects(Users) and Objects(Files) are organized in a non-
discretionary fashion, with respect to different layers of secrecy.
Once the access-list is built, then it should be applied to inbound or outbound of the
interface:
Standard Access-list –
These are the Access-list that are made using the source IP address only. These ACLs
permit or deny the entire protocol suite. They don’t distinguish between the IP traffic such
as TCP, UDP, HTTPS, etc. By using numbers 1-99 or 1300-1999, the router will understand
it as a standard ACL and the specified address as the source IP address.
These are the ACL that uses source IP, Destination IP, source port, and Destination port.
These types of ACL, we can also mention which IP traffic should be allowed or denied.
These use range 100-199 and 2000-2699.
Numbered access-list – These are the access list that cannot be deleted specifically once
created i.e if we want to remove any rule from an Access-list then this is not permitted in
the case of the numbered access list. If we try to delete a rule from the access list then
the whole access list will be deleted. The numbered access-list can be used with both
standard and extended access lists.
Named access list – In this type of access list, a name is assigned to identify an access list.
It is allowed to delete a named access list, unlike numbered access list. Like numbered
access lists, these can be used with both standards and extended access lists.
The standard Access-list is generally applied close to the destination (but not
always).
The extended Access-list is generally applied close to the source (but not always).
We can assign only one ACL per interface per protocol per direction, i.e., only one
inbound and outbound ACL is permitted per interface.
We can’t remove a rule from an Access-list if we are using numbered Access-list.
If we try to remove a rule then the whole ACL will be removed. If we are using
named access lists then we can delete a specific rule.
Every new rule which is added to the access list will be placed at the bottom of the
access list therefore before implementing the access lists, analyses the whole
scenario carefully.
As there is an implicit deny at the end of every access list, we should have at least
a permit statement in our Access-list otherwise all traffic will be denied.
Standard access lists and extended access lists cannot have the same name.
Advantages of ACL –