Protect Application ICT
Protect Application ICT
Protecting Application
or System Software
aji
e b oH
e f a H
M u st e t
ns p . m
o ege.ed u .
te i a i l .c
D e pu @ g m icecoll
B y a il r20 09 iapol
a
E-m filenb a@orom 6591
u s tef 91128
m 0
h on e
e p
Tel
This module includes the following Learning Guides
• LG1: Ensure User Accounts are Controlled LG Code: ICT ITS1 M09LO1LG33
•LG2: Detect and Remove Destructive Software LG Code: ICT ITS1 M09 LO2LG34
•LG3: Identify and Take Action to Stop Spam LG Code: ICT ITS1 M09 LO3 – LG35
LG 1: Ensure User
Accounts are Controlled
This learning guide is developed to provide you the necessary
information regarding the following content coverage and topics –
Physical access
Authentication
Authorization
Physical Access
• The first layer of management and security is the physical access to the computer. To prevent u n a u t h o r i z e d
access, a company may make use of:
locks on the front doors
locks on each floor
locks on offices, etc
security guards
cameras
keys on computer systems.
Only those who have permission and keys will be able to access a computer in the company’s premises. The
Internet, however, presents issues concerning access to corporate information or systems because physical
restrictions cannot be imposed.
Authentication
•Authentication is the process of confirming the identity of a user. This is usually the initial step in
the security process. To confirm the user's identity, the user must present physical or nonphysical
evidence (information) to the authentication platform. These can be divided broadly among the
following:
•What they have: The possession of a physical object, such as a key, keycard, key fob, or swipe
card.
•What they know: Information that only the user would know, including a password, passcode,
personal identification number (PIN), date of birth, Social Security number, or other personally
identifiable information (PII).
• Who they are: Bio-metrics, or the use of an index finger, thumb, hand, voice, retina, face, or
another unique physical identifier to gain access to a resource. The physical attribute must match
what was used at the time of the user's enrollment in the system.
Cont…
1.Knowledge: This is the factor users are most familiar with. The user
is prompted to supply information they know, such as a password,
personal identification number (PIN), security key, or the answer to a
security question.
2.Possession: This factor verifies the user’s identity using something
they possess. For example, by sending a code to a mobile phone.
3.Inherence: This factor verifies the person by some unique personal
attribute, such as biometric authentication or voice recognition.
Other authentication methods include:
Username with static passwords - the password stays the same until changed by the user at some time
Usernames with dynamic passwords - the password is constantly changed by a password generator
synchronized with the user and system.
Other challenge response systems - this may involve PINs, questions to the user requiring various answers or
actions
Certificate Based - this requires the user to have an electronic certificate or token. This may also need to be
digitally signed by a trusted authority.
Physical devices - these include the use of smart cards and biometric. Generally, the entire authentication
process occurs on the local workstation, thus eliminating the need for a special server.
• Whatever method is used is determined by the organizational policy and security requirements.
Authorization
• Authorization is the process of giving a user permission to access a physical location
or information-based resource (e.g., a document, database, application, or website).
• Authorization is unfortunately used synonymously with authentication, but this is an
error. Authentication occurs first, followed by authorization. Users need to prove
their identities before a system can grant them permission to enter.
• However, permission is a broad term. A user may pass authentication procedures and be
granted access to a system, but that does not mean they can access all the components
of an application or online service because specific permissions can be defined by the
organization that allowed them access.
• Permissions are what a user is able to see or do on a website or inside an application.
Without these specific permissions, every user would have access to the same
information or features.
• As such, permissions and restrictions, and their proper administration, are critical to an
organization's security for several reasons.
This is because they:
• prevent a User from Accessing Another Customer's Account
• Block Free Accounts from Receiving the Benefits of Premium Features
• Ensure Zero Crossover Between External Client Accounts and Internal Accounts
The Network and System administrators are responsible for the technical configuration of network operating
systems, directory services and applications. Part of the configuration includes security settings that authorize
user access. The administrators use an organizational policy to determine these settings.
Key differences between Authentication and Authorization?
Authentication
• Authentication is the process of verifying user Authorization
identity before giving them permission to access • Authorization is the process of verifying a
a system, account, or file. user’s access level to a system, account, or
• Its main purpose is to verify (“authenticate”) a file.
user’s identity. It also keeps out suspicious or • User authorization ensures that only
malicious users since their identities will not be authorized users can access the assets they
verifiable. need and only to the extent allowed by the
• Most authentication mechanisms are based on system.
verifying a user’s credentials before they get access • Computer systems can leverage many types
to the system. These credentials may be their of authorization strategies, such as Role-
username and password, security questions or a Based Access Control (RBAC).
one-time pin (OTP) sent to their mobile phones. • Under RBAC, authorization permissions are
• Credential-based authentication works by associated with roles, not users. It ensures
comparing user-provided credentials to a database that users can only access the required
record. When there is a perfect match between the information according to their roles.
two, users can access the account.
Finaly
User Account
• A user account is a collection of information that tells
Windows which files and folders you can access, what
changes you can make to the computer, and your personal
preferences, such as your desktop background or screen
saver. User accounts let you share a computer with several
people, while having your own files and settings. Each
person accesses his or her user account with a username and
password.
Cont…
• A user account is an account assigned to an individual user to
access a system. It typically requires a username and
password for authentication and is used by a single person.
User accounts should have limited permissions based only on
a user's role and job responsibilities.
There are three types of accounts.
On Windows-based operating systems, your user account type controls
what tasks you can perform on your computer, in some cases you may
need administrative rights to perform some tasks or to use some
applications. The following describes the three types of accounts on
Windows-based computers and then helps to determine your user
account type.
• Standard User accounts are for everyday computing.
• Administrator accounts provide the most control over a computer,
and should only be used when necessary.
• Guest accounts are intended primarily for people who need
temporary use of a computer.
Why is User Account Control necessary
• The most important rule for controlling access to resources is to provide
the least amount of access privileges required for users to perform their
daily tasks.
• Many tasks do not require administrator privileges. However, because
previous versions of Windows created all user accounts as administrators
• by default, users logged on to their computers with an administrator
account.
• Without User Account Control (UAC), when a user is logged on as an
administrator, that user is automatically granted full access to all system
resources.
How UAC Work
• there are two levels of users: standard users and administrators.
Standard users are members of the Users group and administrators are
members of the Administrators group on the computer.
• Both standard users and administrators access resources and run
applications in the security context of standard users by default. When a
user logs on to a computer, the system creates an access token for the
user.
• This access token contains information about the level of access that the
user is granted, including specific Security Identifiers (SIDs) and Windows
privileges.
cont...
• When an administrator logs on, two separate access tokens are created for
the user:
• a standard user access token and an administrator access token.
• The standard user access token contains the same user-specific information as
the administrator access token, but the administrative Windows privileges
and SIDs are removed.
• The standard user access token can start standard user applications but
cannot start applications that perform administrative tasks.
• When the user needs to run applications that perform administrative tasks
(administrator applications), the user is prompted to change or elevate the
security context from a standard user to an administrator.
• This default user experience is called Admin Approval Mode. In this mode,
applications require specific permission to run as an administrator application.
User Account Configuration