Logical Access Control refers to the mechanisms and policies that restrict access to computer systems, data, applications, and programs based on the identity and authorisation of users. Unlike physical access controls that prevent unauthorised physical entry, logical access controls operate at the software and system level to ensure that only authorised individuals can access specific resources, perform certain functions, or view particular data.
Logical access controls are designed to achieve the following objectives:
1. Identification and Authentication: Every user must be uniquely identified (through user IDs) and authenticated (through passwords, PINs, biometrics, tokens, or multi-factor authentication) before gaining access to any system resource. This ensures accountability and traceability of all user actions.
2. Authorisation: Once authenticated, the system grants access rights based on the user's role, responsibilities, and need-to-know principle. This determines what resources a user can access and what operations (read, write, modify, delete) they can perform.
3. Access Control Lists (ACLs): These are matrices or tables that define the access privileges of each user or group of users to specific system resources, files, programs, and data.
4. Audit Trails and Logs: Logical access controls maintain logs of all access attempts — successful and unsuccessful — enabling monitoring, detection of suspicious activities, and forensic investigation.
5. Principle of Least Privilege: Users are granted only the minimum level of access required to perform their job functions, thereby reducing the risk of accidental or intentional misuse.
---
User Access Management Controls for Technical Exposures are specific controls implemented to manage user access and mitigate technical vulnerabilities. These include:
1. Password Controls: Passwords must meet minimum length and complexity requirements (combination of letters, numbers, and special characters). Passwords should be encrypted during storage and transmission. Systems should enforce periodic password changes and prevent reuse of old passwords. Account lockout policies should be enforced after a defined number of failed login attempts to prevent brute-force attacks.
2. User Registration and De-registration: A formal process must exist for granting and revoking access. When an employee joins, transfers, or leaves the organisation, access rights must be promptly updated or revoked to prevent unauthorised access by ex-employees or misuse of dormant accounts.
3. Review of User Access Rights: Periodic review (e.g., quarterly or half-yearly) of user access rights should be conducted to ensure that access privileges remain appropriate. Excessive or outdated privileges should be revoked promptly — this is known as access recertification.
4. Segregation of Duties (SoD): Access controls should enforce segregation of duties to prevent any single individual from performing incompatible functions. For example, the person who initiates a payment should not also be the one who authorises it. SoD reduces the risk of fraud and errors.
5. Use of System Utilities: Access to powerful system utilities (e.g., those that can bypass normal application controls, modify data directly in the database) must be strictly restricted and monitored. Such utilities should only be accessible to authorised system administrators and only for legitimate purposes.
6. Time-Based Access Controls: Access to certain systems or sensitive data may be restricted to specific time windows (e.g., business hours only). Access outside these windows triggers alerts, reducing the risk of after-hours unauthorised access.
7. Remote Access Controls: For users accessing systems remotely (e.g., through VPNs or remote desktop), additional controls such as multi-factor authentication, encrypted connections, and session timeouts must be enforced.
8. Privileged Access Management (PAM): Privileged accounts (such as system administrators or database administrators) have elevated access rights and therefore pose higher risk. These accounts must be subject to enhanced monitoring, dual authorisation, and regular review.
9. Dormant Account Management: Accounts that have been inactive for a defined period (e.g., 30 or 90 days) should be automatically disabled or flagged for review, as dormant accounts are a common target for exploitation.
10. Audit and Monitoring: All access activities — especially privileged access, failed login attempts, and access to sensitive data — must be logged and regularly reviewed by an independent security team or internal auditor to detect anomalies and policy violations.
In conclusion, logical access controls combined with robust user access management controls form the first line of defence in protecting an organisation's IT environment against technical exposures such as unauthorised data access, data theft, system manipulation, and fraud.