Chapter 4 - Identity and Access Management Part 1 - Section A
Chapter 4 - Identity and Access Management Part 1 - Section A
1
Chapter 4: Identity and Access Management Part 1 - Section A
data, programs, applications) and are applied ● Organizations should establish such basic
when the subject resource is needed. criteria for assigning technical access to
● How to determine if access is to be allowed specific data, programs, devices and resources,
(i.e., the information that users can access, the including who will have access and what level
programs or transactions that they can run, of access they will
and the modifications that they can make): ● Example: access to information in the daily
a) Based on the identification and calendar of meetings
authentication of the user that requires a ○ It may be desirable for everyone in the
given resource organization to have access to specific
b) Analyzing the security profile of the user information on the system such as the
and resource data displayed on an organization’s daily
● Such controls may be built into the operating calendar of meetings.
system (OS), invoked through separate ● The program that formats and displays the
access control software and incorporated calendar might be modifiable by only a few
into application programs, database, network system administrators, while the OS
control devices and utilities (e.g., real-time controlling that program might be directly
performance Logical system access controls: accessible by still fewer.
built into the OS, invoked through access
control software, incorporated into programs,
FOUR LAYERS OF IT ASSETS UNDER
databases, network control devices and utilities
LOGICAL SECURITY
(e.g., real-time performance monitors).
1. Networks
2. Platforms
Logical Resources of the System 3. Databases
1) transactions 4. Applications
2) data
3) programs ● Layered security: provides greater scope and
4) applications granularity of control to information
resources.
Examples of Access Requests to System ● Example: Network and platform layers:
a) access on the information that users can Provide pervasive general systems control
access over users authenticating into systems,
b) access on the programs or transactions that system software and application
users can run configurations, data sets, load libraries, and
c) access on the modifications that users can any production data set libraries.
make ● Database and application controls: provide
a greater degree of control over user activity
PHYSICAL AND LOGICAL SYSTEM ACCESS within a particular business process by
● Physical or logical system access (to any controlling access to records, specific data
computerized information): should be on a fields and transactions.
documented need-to-know basis; least
privilege RECITATION QUESTION #2:
○ Need-to-know basis: often referred to as Question: What are the layers of logical security
role-based where there is a legitimate over the IT assets? (provide at least one answer)
business requirement based on least Answer:
privilege. ● Network layer
● Other considerations for granting access: ● Platform layer
accountability (e.g., unique user ID) and ● Database layer
traceability (e.g., logs) ● Application layer
● IS auditor to evaluate appropriateness of
criteria
○ These principles should be used by IS INFORMATION OWNER OR MANAGER
auditors when they evaluate the ● is responsible for the accurate use and
appropriateness of criteria for defining reporting of information
permissions and granting security
privileges.
2
Chapter 4: Identity and Access Management Part 1 - Section A
● should provide written authorization for ○ Information asset owners: should review
users or defined roles to gain access to access controls periodically with a
information resources under their control. predetermined authorization matrix
● Manager: should handover this that defines the least-privileged access
documentation directly to the security level and authority for an individual/role
administrator to ensure that mishandling or with reference to his/her job roles and
alteration of the authorization does not occur. responsibilities.
● Need to update access, if there is excess
LOGICAL ACCESS CAPABILITIES access
● Logical access capabilities: are implemented ○ Any access exceeding the access
by security administration in a set of access philosophy in authorized matrix or in
rules that stipulate which users (or groups of actual access levels granted on a system
users) are authorized to access a resource at should be updated and changed
a particular level (e.g., read-, update- or accordingly.
execute-only) and under which conditions ● One of the good practices: to integrate the
(e.g., time of the day or a subset of computer review of access rights with human resource
terminals). processes.
● Security administrator: invokes the ● When an employee transfers to a different
appropriate system access control mechanism function (i.e., promotions, lateral transfers or
upon receipt of a proper authorization request demotions), access rights are adjusted at
from the information owner or manager to the same time.
grant a specified user the rights for access to, ● Development of a security-conscious culture
or use of, a protected resource. increases the effectiveness of access controls.
● IS auditor: should be aware that access is
granted to the organization’s information Causes/Reasons for Access Authorization
systems using the principles of need-to-know, Problems (which can impact effectiveness of
least privilege and SoD. access controls)
1) personnel and departmental changes
Relevant Principles on Logical Access to 2) malicious efforts
System 3) plain carelessness
a) need-to-know (role-based)
b) principle of least privilege (POLP) NONEMPLOYEES
c) segregation of duties ● Nonemployees with access to corporate IS
resources should also be held responsible for
Principle of Least Privilege (POLP) security compliance and be accountable for
● Limiting access rights to minimum security breaches.
permissions (needed to do work/task)
● Least amount of privilege necessary
RECITATION QUESTION #3:
Question: When should the security
REVIEW OF ACCESS AUTHORIZATION administrator invoke the appropriate system
● Should be evaluated regularly to ensure that access control mechanism?
they are still valid. Answer: Upon the receipt of a proper
● Personnel and departmental changes, authorization request from the information
malicious efforts, and just plain owner or manager
carelessness: result in authorization creep
and can impact the effectiveness of access
controls. WHO ARE THE NON-EMPLOYEES?
● Increase in risk when access is not removed
● include contract employees, vendor
whenever a personnel leaves the organization
programmers/analysts, maintenance
○ Many times, access is not removed when
personnel, clients, auditors, visitors and
personnel leave an organization, thus
consultants.
increasing the risk of unauthorized access.
● It should be understood that nonemployees
● Need for periodic review of access control
are also accountable to the organization’s
based on authorization matrix
security requirements.
3
Chapter 4: Identity and Access Management Part 1 - Section A
4
Chapter 4: Identity and Access Management Part 1 - Section A
5
Chapter 4: Identity and Access Management Part 1 - Section A
6
Chapter 4: Identity and Access Management Part 1 - Section A
7
Chapter 4: Identity and Access Management Part 1 - Section A