Access Control Policy

Default Logo
Max 4 MB | PNG, JPG

Access Control Policy

Company Name:

Effective Date:

Policy Owner:

Approved By:

Chief Information Security Officer:

1. Purpose & Scope

1.1 This policy establishes the Organization's comprehensive framework for managing logical and physical access to information systems, applications, data, networks, and facilities. The policy ensures that access rights are granted, modified, and revoked based on the principles of least privilege and need-to-know, minimising the risk of unauthorised access, data breaches, and insider threats. This policy is aligned with ISO 27001 Annex A.9 Access Control requirements, NIST SP 800-53 access control family, and applicable data protection and privacy regulations.

1.2 This policy applies to all logical and physical access to the Organization's information assets, including servers, workstations, network devices, applications, databases, cloud services, and physical facilities, whether by employees, contractors, consultants, temporary workers, third-party service providers, or automated systems and processes. The policy covers access across all environments including on-premise data centres, cloud infrastructure, hybrid environments, remote access, and mobile access. All individuals and systems that require access to Organization resources must comply with this policy, and access shall not be granted until the requirements defined herein have been satisfied.

1.3 The Chief Information Security Officer shall be responsible for establishing access control standards, defining role-based access models, approving access control technologies, and monitoring compliance with this policy across the Organization. Data owners, defined as the business unit leaders or functional heads with accountability for specific systems or data domains, shall be accountable for authorising access to the systems and data within their domain and for certifying the continued appropriateness of granted access on a periodic basis. The Identity and Access Management team within the IT department shall administer the Organization's access control infrastructure, process access requests, and execute access provisioning and de-provisioning activities in accordance with this policy.

2. Access Provisioning & Role-Based Access

2.1 Access to Organization systems, applications, and data shall be provisioned exclusively through a formal request and approval process managed through the Organization's identity governance platform or IT service desk. Access requests shall specify the systems, applications, and data resources required, the level of access needed including read, write, or administrative privileges, the business justification for the access, the anticipated duration of access, and the approving data owner or system owner. Access shall not be provisioned on the basis of verbal requests, informal communications, or self-service registration unless the system has been specifically approved for self-service access by the CISO. The IAM team shall process approved access requests within 2 business days and shall verify that the requested access is consistent with the user's role and the principle of least privilege.

2.2 The Organization shall implement role-based access control as the primary access management model, where access permissions are assigned to defined roles that correspond to job functions, rather than to individual users. Role definitions shall be developed by the IAM team in collaboration with data owners and business unit leaders, and shall specify the minimum set of permissions required for each job function. Each role shall be documented with a clear description of its purpose, the systems and data it grants access to, and the level of access provided. Role assignments shall be reviewed by data owners at least annually to ensure continued alignment with business requirements and the principle of least privilege. Where a user requires access that exceeds their assigned role, a supplementary access request shall be submitted with a specific business justification and shall be subject to approval by the relevant data owner and the IAM team.

2.3 Segregation of duties shall be enforced across all critical business processes and systems to prevent any single individual from having a combination of access rights that could enable them to initiate and approve transactions, create and review their own work, administer systems and audit their own administrative activity, or perform any other combination of conflicting duties that could result in fraud, error, or abuse without independent oversight. The IAM team shall maintain a segregation of duties conflict matrix that identifies prohibited access combinations, and the identity governance platform shall enforce these rules automatically during access provisioning. Where a segregation of duties conflict is identified, the request shall be escalated to the relevant data owner and the CISO for review and, if necessary, the implementation of compensating controls such as enhanced monitoring or dual-approval workflows.

2.4 Temporary access, defined as access required for a limited period to support a specific project, task, or engagement, shall be provisioned with an explicit expiration date and shall be automatically revoked by the identity governance platform upon expiry. Extensions of temporary access shall require a new access request and approval. Emergency access, also known as break-glass access, may be granted outside the standard approval process in situations where immediate access is required to respond to a critical incident or prevent significant business disruption. Emergency access shall be provisioned by the IAM team or designated on-call personnel, logged in detail including the requestor, authoriser, systems accessed, and actions performed, reviewed by the relevant data owner and the CISO within 24 hours of provisioning, and revoked immediately when no longer required or within a maximum of 72 hours, whichever is sooner.

3. Access Review & Certification

3.1 Access rights for all systems containing Confidential or Restricted data, as defined in the Organization's Data Management Policy, shall be reviewed at least quarterly. Access rights for all other systems shall be reviewed at least semi-annually. Data owners shall be responsible for certifying the continued appropriateness of each user's access during these reviews, confirming that the user still requires the access, the level of access remains consistent with the user's current role, and no segregation of duties conflicts have been introduced. Access reviews shall be conducted through the Organization's identity governance platform, which shall generate review campaigns, track reviewer responses, and automatically flag accounts with incomplete reviews or overdue certifications. Access that is not certified during the review period shall be automatically suspended pending data owner confirmation.

3.2 Access rights shall be modified or revoked promptly in response to changes in an employee's role, responsibilities, or employment status. Specifically, when an employee transfers to a different department or assumes a new role, access rights associated with the previous role shall be reviewed and, where no longer required, revoked within 5 business days of the effective date of the change. When an employee begins extended leave exceeding 30 days, their access shall be suspended for the duration of the leave and reactivated upon their return, subject to re-verification. When an employee is subject to disciplinary proceedings that warrant access restriction, the IT department shall restrict access within 4 hours of receiving a request from Human Resources. The IAM team shall coordinate with Human Resources to receive timely notification of all role changes, transfers, leaves, and disciplinary actions that may affect access requirements.

3.3 The IAM team shall implement automated monitoring to identify dormant user accounts that have not recorded any authentication or activity for 90 consecutive days. Dormant accounts shall be automatically disabled, and the account owner and their line manager shall be notified. If the account owner does not request reactivation with a valid business justification within an additional 90 days, the account shall be permanently deleted from the Organization's directory services and all associated access rights shall be revoked. The IAM team shall generate a monthly dormant account report and shall present the report to the CISO, highlighting any accounts belonging to privileged users or accounts with access to Restricted data. Exceptions to the dormant account policy, such as accounts required for seasonal or cyclical business activities, shall be documented and approved by the relevant data owner and the CISO.

4. Physical Access Control

4.1 Physical access to the Organization's facilities shall be controlled through a combination of electronic access control systems, visitor management procedures, and security personnel, with the level of control proportionate to the sensitivity of each area. General office areas shall be secured by electronic badge access requiring a valid employee or contractor access badge. Restricted areas, including data centres, server rooms, network closets, and executive areas, shall require additional authentication such as PIN entry, biometric verification, or two-person access rules. The Facilities Management team shall administer the physical access control system in coordination with the IT department and the CISO, and shall conduct quarterly reviews of physical access rights to ensure that only authorised individuals have access to restricted areas.

4.2 All visitors to Organization facilities shall be pre-registered by their host employee through the visitor management system, shall present government-issued photo identification upon arrival, and shall be issued a temporary visitor badge that is clearly distinguishable from employee badges. Visitors shall be escorted by their host or an authorised employee at all times while on the premises and shall not be left unattended in work areas. Visitor access shall not extend to restricted areas, including data centres, server rooms, or areas containing Confidential or Restricted data, without explicit prior approval from the area manager and the CISO. The reception or security desk shall maintain a visitor log recording the visitor's name, organization, host employee, arrival time, departure time, and areas visited. Visitor badges shall be collected upon departure, and the Facilities Management team shall reconcile visitor badges daily.

4.3 All physical access events, including badge swipes, biometric authentications, denied access attempts, and door-held-open alerts, shall be logged by the electronic access control system with timestamps, user identification, and location details. Access logs shall be retained for a minimum of 12 months, or for such longer period as may be required by applicable regulations or the Organization's data retention schedule. The security team shall review physical access logs for anomalies, including access attempts outside normal business hours, repeated denied access attempts, tailgating alerts, and access to restricted areas by individuals whose access has not been verified. Anomalous events shall be investigated within 24 hours, and confirmed security incidents shall be reported to the CISO and managed in accordance with the Organization's incident response procedures.

5. Compliance & Policy Review

5.1 The IAM team shall produce monthly access management metrics and present them to the CISO and the IT Department Head. Metrics shall include access request provisioning turnaround times and adherence to the 2-business-day service level, access review campaign completion rates by data owner and system, dormant account identification and remediation statistics, segregation of duties violations detected and resolved, emergency and temporary access events and their post-event review status, and physical access anomaly investigation outcomes. Trends and patterns identified through these metrics shall inform risk assessments, resource allocation decisions, and continuous improvement initiatives for the Organization's access control program.

5.2 Any violation of this policy, including but not limited to gaining or attempting to gain unauthorised access to systems or facilities, sharing access credentials, failing to complete assigned access review certifications, circumventing access controls or segregation of duties requirements, or failing to report suspected unauthorised access, shall be subject to disciplinary action proportionate to the nature, severity, and impact of the violation. Disciplinary measures may include mandatory security retraining, temporary suspension of access privileges, formal written warning, suspension from employment, or termination of employment. All violations shall be documented and investigated in coordination with the Information Security team, Human Resources, and, where appropriate, Legal Counsel.

5.3 This policy shall be reviewed comprehensively at least once every 12 months by the CISO, in consultation with the IAM team, data owners, the Facilities Management team, and Legal Counsel. Reviews shall assess the policy's effectiveness in the context of changes to the Organization's access control infrastructure, identity governance platform capabilities, threat landscape, organizational structure, and regulatory requirements including ISO 27001 certification audit findings. Interim reviews shall be triggered by significant access-related security incidents, deployment of new access control technologies, organizational restructuring, or material regulatory changes. Approved amendments shall be communicated to all employees and stakeholders at least 14 calendar days before the effective date, and all access provisioning and review processes shall be updated to reflect the amended policy requirements.

What Is an Access Control Policy?

An access control policy is a formal document that defines how an organization manages who can access its information systems, applications, data, and physical facilities, and under what conditions. It establishes the principles, procedures, and technical controls that govern the provisioning, modification, review, and revocation of access rights.

Access control is one of the most critical domains in information security. ISO 27001 dedicates an entire Annex A section (A.9) to access control, covering business requirements for access, user access management, user responsibilities, and system and application access control. NIST SP 800-53 defines a comprehensive access control family with dozens of individual controls.

The policy is built on two foundational principles: least privilege, which ensures that users are granted only the minimum access necessary to perform their duties, and need-to-know, which restricts access to information based on a legitimate business requirement. Together, these principles minimise the attack surface and limit the potential impact of compromised accounts or insider threats.

Why Your Organization Needs an Access Control Policy

A formal access control policy is essential for preventing unauthorised access to sensitive systems and data, which is the objective of the majority of cyber attacks. Without standardised access management procedures, organizations accumulate excessive access rights, dormant accounts, and uncontrolled privileged access that create easily exploitable vulnerabilities.

Access control failures are a leading cause of data breaches. The OWASP Top 10 consistently ranks broken access control as one of the most common and severe web application security risks. Verizon's Data Breach Investigations Report finds that privilege misuse and access abuse are significant factors in insider-driven breaches. A formal policy that enforces least privilege, segregation of duties, and regular access reviews directly addresses these risks.

Regulatory compliance is another compelling driver. SOX requires segregation of duties in financial systems. HIPAA mandates that access to protected health information be limited to the minimum necessary. PCI DSS requires restriction of access to cardholder data on a need-to-know basis. GDPR requires appropriate technical measures including access controls proportionate to the data being protected. A documented access control policy is the foundation for demonstrating compliance with all of these requirements.

Physical access control is equally important. Unauthorised physical access to data centres, server rooms, and sensitive work areas can bypass logical security controls entirely. A comprehensive policy addresses both logical and physical access management.

Key Components of an Access Control Policy

A comprehensive access control policy addresses four key domains that together provide end-to-end access governance.

The first domain is Access Provisioning and Role-Based Access. This defines the formal request and approval process for granting access, the role-based access control model that assigns permissions to roles rather than individuals, segregation of duties requirements, and procedures for temporary and emergency access.

The second domain is Access Review and Certification. This establishes the periodic review cycle in which data owners certify that each user's access remains appropriate. It also defines the triggers for access modification, such as role changes and departures, and the procedures for identifying and disabling dormant accounts.

The third domain is Physical Access Control. This covers facility security measures including electronic badge access, restricted area protections, visitor management procedures, and physical access event logging.

The fourth domain is Compliance and Metrics. This defines the access management metrics that are tracked and reported, the consequences of policy violations, and the policy review cycle.

How to Implement This Access Control Policy

Implementing this access control policy requires investment in identity governance technology, clear role definitions, and commitment to periodic access reviews.

Step one: define your role model. Work with business unit leaders to define the roles that correspond to job functions across the organization. For each role, specify the systems, applications, and data that the role requires access to, and the level of access needed. This role model becomes the foundation for automated provisioning.

Step two: deploy identity governance. Implement an identity governance platform that automates access request workflows, enforces approval chains, manages role assignments, and runs access review campaigns. The platform should integrate with your directory services, HR system, and critical applications.

Step three: build the segregation of duties matrix. Identify the access combinations that create conflict-of-interest or fraud risks, and configure your identity governance platform to enforce these rules automatically during provisioning.

Step four: launch access reviews. Configure and execute your first access review campaign, with data owners certifying the access rights of all users within their domain. Target quarterly reviews for systems containing Confidential or Restricted data and semi-annual reviews for all other systems.

Step five: address physical access. Ensure that electronic access control systems, visitor management procedures, and restricted area protections are aligned with the policy requirements. Integrate physical access provisioning and de-provisioning with the HR offboarding workflow.

Frequently  Asked  Questions

What is the principle of least privilege?

The principle of least privilege requires that users are granted only the minimum access rights necessary to perform their assigned job duties. This minimises the potential damage from compromised accounts, reduces insider threat risk, and ensures compliance with data protection regulations that require proportionate access controls.

How are access rights provisioned?

Access is provisioned through a formal request and approval process managed through the organization's identity governance platform. Requests must specify the systems, access level, business justification, and duration needed. Approval is required from the user's manager and, for sensitive systems, the relevant data owner. Requests are processed within 2 business days.

What is role-based access control?

Role-based access control assigns permissions to defined roles that correspond to job functions, rather than to individual users. Each role specifies the minimum set of system and data permissions required for that function. Users are assigned to roles, and their access is automatically configured. This approach simplifies management and ensures consistency.

How often are access rights reviewed?

Access rights for systems containing Confidential or Restricted data are reviewed quarterly. Access rights for all other systems are reviewed semi-annually. Data owners certify the continued appropriateness of each user's access during these reviews. Access that is not certified is automatically suspended.

What happens to my access when I change roles?

When you change roles or transfer departments, access rights associated with your previous role are reviewed and, where no longer required, revoked within 5 business days. New access aligned with your new role is provisioned through the standard request and approval process. This prevents the accumulation of excessive access over time.

What is segregation of duties?

Segregation of duties prevents any single individual from having access rights that could enable them to perform conflicting activities, such as initiating and approving transactions, without independent oversight. The identity governance platform enforces a conflict matrix automatically during provisioning and flags violations for review.

What are the rules for visitor access to facilities?

All visitors must be pre-registered, present photo identification, and receive a temporary visitor badge. Visitors must be escorted at all times and cannot access restricted areas without explicit approval from the area manager and the CISO. Visitor badges are collected upon departure and reconciled daily.

How often is the access control policy reviewed?

The policy is reviewed at least annually by the CISO in consultation with the IAM team, data owners, the Facilities Management team, and Legal Counsel. Reviews assess the policy's effectiveness in the context of infrastructure changes, threat landscape evolution, and regulatory requirements.
Adithyan RKWritten by Adithyan RK
Surya N
Fact Checked by Surya N
Published on: 3 Mar 2026Last updated:
Share now: