ISMS - 005 Access Control Policy
ISMS - 005 Access Control Policy
Version: 1.0
Disclaimer: No Part of this document may be reproduced or transmitted in any form or by any means,
electronic, manual, photocopying, recording or by any information storage and retrieval system, without
prior written permission of AXIS INSURANCE BROKERS.
Restricted
AIB-IS-POL-05 Clear Desk and Clear Screen Policy
Document Control
Document Information
Classification Restricted
First Adam
V 1.0 14/09/2023 Draft Sufyan Areed
Release Ahmed
First Adam
V 1.0 02/10/2023 Approved Sufyan Areed
Release Ahmed
Draft Verification
Date of
Name Designation Signature
Verification
Sufyan 02/10/202
Sufyan Areed CTO
Areed 3
Approvals
Sufyan
Sufyan Areed CTO
Areed 02/10/2023
Abbreviations
Term Description
IT Information Technology
HR Human Resource
QA Quality Assurance
Table of Contents
1 Introduction.................................................................................................................................................5
2 Scope........................................................................................................................................................... 5
3 Purpose........................................................................................................................................................6
4 Roles And Responsibilities............................................................................................................................6
BUSINESS OWNERS......................................................................................................................................................6
5 Acess Control Policy.....................................................................................................................................7
5.1 GENERAL CONTROLS...........................................................................................................................................7
5.2 PHYSICAL ACCESS CONTROL.................................................................................................................................7
5.3 LOGICAL ACCESS CONTROL..................................................................................................................................8
5.3.1 User Registration And Deregistration..................................................................................................8
5.3.2 User Identification And Authentication................................................................................................9
5.3.3 Service Accounts..................................................................................................................................9
5.3.4 User Authorization...............................................................................................................................9
5.3.5 User Logon Process............................................................................................................................10
5.3.6 User Access Modifications.................................................................................................................10
5.3.7 Administrator Access Modifications..................................................................................................10
5.3.8 Local Administrator Access................................................................................................................11
5.3.9 Temporary Accounts..........................................................................................................................11
5.3.10 Third Party Access.........................................................................................................................11
5.3.11 Automatic Logoff..........................................................................................................................11
5.3.12 Termination Of Access..................................................................................................................12
5.3.13 Privileged User Accounts...............................................................................................................12
5.3.14 Super Administrators....................................................................................................................13
5.3.15 Review Of User Access Rights.......................................................................................................13
6 Policy Compliance, Enforcement And Violations........................................................................................13
7 References.................................................................................................................................................14
1 Introduction
The control of access to our information assets is a fundamental part of a defence in depth strategy to
information security at Axis Insurance Brokers. If we need to effectively protect the confidentiality,
integrity and availability of data, then we must ensure that a comprehensive mix of physical and logical
controls are in place.
The security classification of the information stored and processed by a particular system or
service
Relevant legislation that may apply e.g. the NESA
The regulatory framework in which the organization and the system operates
Contractual obligations to external third parties
The threats, vulnerabilities and risks involved
The organization’s appetite for risk
In addition to the specific requirements, a number of general principles will be used when designing
access controls for Axis Insurance Brokers’ systems and services. These are:
Defence in Depth – security should not depend upon any single control but be the sum of a
number of complementary controls
Least Privilege – the default approach taken should be to assume that access is not required,
rather than to assume that it is
Need to Know – access is only granted to the information required to perform a role, and no
more
Need to Use – Users will only be able to access physical and logical facilities required for their
role
Adherence to these basic principles will help to keep systems secure by reducing vulnerabilities and
therefore the number and severity of security incidents that occur.
The access control policy has been segregated into two parts namely Physical Access Control and Logical
Access Control.
2 Scope
This policy is applicable to all users of Axis Insurance Brokers’ information, Information Technology (IT)
equipment’s, systems, assets, resources and information processing facilities.
3 Purpose
Access control systems are in place to protect the interests of all authorized users of Axis Insurance
Brokers information systems by providing a safe, secure and accessible environment in which to work.
To secure and protect the logical and physical access to Axis Insurance Brokers’ information,
information processing facilities and resources.
IT Department
▪ Creating user accounts and granting access based on the
business requests
▪ Maintaining records
HR Department
▪ Communicating the changes in the Human Resource structure of
Axis Insurance which includes but not limited to; New Staff
Joining, Staff Separation and Staff movements from one
department to another
7. All physical access must be logged and made available for review when required.
5.3 Logical Access Control
Access to the IT components and data is generally known as logical access. In other terms, any access to
the Information processing systems should be considered as logical access. Logical access shall provide
Authentication, Authorization an
1. Access to the Axis Insurance IT infrastructure which includes, but not limited to, network
devices, network services, operating systems, applications, databases, data files should be
granted on the basis of business needs.
2. Access should be allowed on the basis of positive identification and positive authorization.
3. Any access to information systems should be denied by default and access permissions are
built, step by step, on a need to know basis or on the concept of least privileges.
4. Access to all data objects, fields, tables or any information shall be checked or validated for
authority.
5. Adequate segregation of duties or separation of privileges within systems should be
incorporated. This will ensure that authority is not focused on a single individual.
1. Users are accountable for all activities performed with their personal user IDs. User IDs
shall not be utilised by anyone other than the individuals to whom they have been issued
except for super administrator accounts.
2. All computers that connect to the Axis Insurance IT infrastructure must make use of
proper access controls that prohibit access to resources without proper authentication
procedures
4. Users shall be provided with a unique User ID combined with a password for
authentication, as a minimum.
5. Users shall be provided with one ID per system or application with the appropriate
privileges mapped to carry out their day to day activities.
6. IT Administrators shall assign unique user identification to the authorized user upon
notification of access request approval.
1. Service Accounts are user accounts used by applications to run a specific application. The
ownership and accountability of such user account should be with the application
custodian.
2. Service accounts shall not be used for performing activities other than the indented and
approved use. These accounts should not be used for individual user activities
3. Service accounts should follow the password policy. However, these accounts may be
exempted from the password expiry requirement, if it is required by the system.
4. Service accounts shall have access only to the systems and/or applications for which these
accounts are created.
1. All access requests to data and systems must be formally authorized. The access granted
shall follow the principles of least privilege, need to know and need to use.
2. Each user must be allocated access rights and permissions to computer systems and data
that are commensurate with the tasks they are expected to perform. In general this
should be role-based i.e. a user account will be added to a group that has been created
with the access permissions required by that job role.
3. Group roles should be maintained in line with business requirements and any changes to
them should be formally authorized and controlled via the change management process.
4. Ad-hoc additional permissions should not be granted to user accounts outside of the
group role; if such permissions are required this should be addressed as a change and
formally requested.
5. Any access requested by a contractor, temporary staff, or third parties must be authorized
by GM/AGM and must be for a limited period, with a defined end date and time. Such
access must be promptly disabled.
1. The Log-on process must advise that access to Axis Insurance information is available to
authorized users only.
2. The Log-on process must not provide any information that would aid an unauthorized
user to successfully Log-on.
3. The unsuccessful Log-on attempts should be recorded and reviewed on a regular basis.
1. Access must be modified as required when employees move internally within Axis
Insurance or on vacation for more than 30 days
2. The IT Departments shall have the authority to disable accounts without reference if
necessary and in such cases; the IT department shall notify the IT Manager about the
change.
1. Third parties, Temporary staff or staff filling a temporary role shall use their own user
identification.
2. If a temporary account is used, the temporary account that is released for use must be for
a limited period with a predefined end date and time.
1. Partner agencies or 3rd party suppliers must not be given details of how to access the
organization’s network without formal approvals from the IT Manager.
2. Access granted to third parties, which includes but not limited to vendors, contractors,
external auditors, etc… should have the supporting business documents which clearly
justify the business needs
3. Third party access must be for a limited period with a predefined end date and time.
5. Partners or 3rd party suppliers must contact the IT on each occasion to request
permission to connect to the network and a log of activity must be maintained. Remote
access software and user accounts must be disabled when not in use.
6. All contracts with third party (such as vendors, contractors and partners) & third parties
shall include security requirements and clauses outlining the access requirements to
ABHNIC systems.
7. The procurement department and the ISO shall review and agree on any special
requirements related to providing access to vendors/consultants and ensure including
such requirements in the contracts/agreements. The ISO reserves the right to require
additional access controls to be applied in relation to any contract.
1. Systems, applications and other computing devices which stores, process or transmit
confidential information should employ inactivity timers or automatic logoff mechanisms.
2. Maximum allowed duration of the inactivity shall be defined based on the risk analysis of
the applications and systems
1. The Employees’ Manager ensures that all such user accounts to access ended.
2. Any client user accounts used by the employee should be disabled or the account
password should be changed.
3. Codes or passwords for systems, equipment access passwords (routers and switches),
administrator passwords, and other common access control information should be
changed when appropriate.
4. Human Resources are promptly notified and the termination processed in accordance
with the separation checklist.
5. In exceptional circumstances where there is perceived to be a risk that the employee may
take action that may harm the organization prior to or upon termination, a request to
remove access may be approved and actioned in advance of notice of termination being
given. This precaution should especially apply in the case where the individual concerned
has privileged access rights e.g. domain admin.
1. System / application administrators shall have a separate named user account for
administrator purpose and used only when the additional privileges are required. They
should use normal user accounts for their day-to-day operations.
2. Generic admin accounts should not be used as they provide insufficient identification of
the user.
3. Access to admin level permissions should only be allocated to individuals whose roles
require them and who have received sufficient training to understand the implications of
their use.
4. The use of user accounts with privileged access in automated routines such as batch or
interface jobs should be avoided where possible. Where this is unavoidable the password
used should be protected and changed on a regular basis.
1. Super administrator user accounts, which are not required for regular usage, shall be
recorded in a secure manner. Procedures shall be established to ensure the accountability
of the usage of these accounts.
2. The password of the Super Administrator account should be known to a single person at
any given point of time
3. Existence of such accounts and the procedures to handle them needs to be approved by
the AGM.
The IT Manager on a quarterly basis to ensure that this policy is being complied with will carry out
a review of user accounts with privileged access.
IT Administrators on a regular basis shall disable user accounts that are inactive for a period of
<<maximum 90 days>>.
All privileged and administrators accounts shall be reviewed on a quarterly basis, and changes to
such accounts shall be logged for periodic review.
If Users are unsure or not clear of anything in this policy, they should seek clarification or advice from
ISO. The ISO reserves the right to check the compliance of this policy on a periodic basis.
Any exceptions to this policy with valid business justification require approval from ISO on a case to case
basis.
The ISO in coordination with the Information Systems Owners, Business Processes Owners reserve the
right to review Users’ lists and ascertain the privileges granted.
The ISO reserves the right to review the use of high privilege ID’s at regular intervals.
7 References