Access Control Policy

Version

1.1

Owner

Head of Engineering

Last Updated on

Jun 27, 2023

Last Updated by

@Bruno Belizario

Approved by

@Sean Oldfield

Purpose

To limit access to information and information processing systems, networks, and facilities to authorized parties in accordance with business objectives.

Scope

All ecoPortal information systems that process, store, or transmit confidential data as defined in the ecoPortal Data Management Policy. This policy applies to all employees of ecoPortal and to all external parties with access to ecoPortal engineering networks and system resources.

Policy

Access to information computing resources is limited to personnel with a business requirement for such access. Access rights shall be granted or revoked in accordance with this Access Control Policy.

 

For any questions relating to this document or our Security & Privacy, please contact us at issues@ecoportal.co.nz


Business Requirements of Access Control

Access Control Policy

ecoPortal shall determine the type and level of access granted to individual users based on the “principle of least privilege.” This principle states that users are only granted the level of access absolutely required to perform their job functions, and is dictated by ecoPortal's business and security requirements. Permissions and access rights not expressly granted shall be, by default, prohibited.

ecoPortal's primary method of assigning and maintaining consistent access controls and access rights shall be through the implementation of Role-Based Access Control (RBAC). Wherever feasible, rights and restrictions shall be allocated to groups. Individual user accounts may be granted additional permissions as needed with approval from the system owner or authorized party.

All privileged access to production systems should use Multi-Factor Authentication (MFA).

Access to Networks and Network Services

The following security standards shall govern access to ecoPortal networks and network services:

  • Technical access to ecoPortal networks must be formally documented including the standard role or approver, grantor, and date

  • Only authorized ecoPortal employees and third parties working off a signed contract or statement of work, with a business need, shall be granted access to the ecoPortal production networks

  • ecoPortal guests may be granted access to guest networks after registering with office staff without a documented request

  • Remote connections to production systems and networks must be encrypted

User Access Management

ecoPortal requires that all personnel have a unique user identifier for system access and that user credentials and passwords are not shared between multiple personnel. Users with multiple levels of access (e.g. administrators) should be given separate accounts for normal system use and for administrative functions wherever feasible. Root, service, and administrator accounts may use a password management system to share passwords for business continuity purposes only. Administrators shall only use shared administrative accounts as needed.

User Registration and Deregistration

Only authorized administrators shall be permitted to create new user IDs, and may only do so upon receipt of a documented request from authorized parties. User provisioning requests must include approval from data owners or ecoPortal management authorized to grant system access. Prior to account creation, administrators should verify that the account does not violate any ecoPortal security or system access control policies such as segregation of duties, fraud prevention measures, or access rights restrictions.

User IDs shall be promptly disabled or removed when users leave the organization or contract work ends. User IDs shall not be re-used.

User Access Provisioning

  • New employees and/or contractors are not to be granted access to any ecoPortal production systems until after they have completed all HR onboarding tasks, which may include but are not limited to the signed employment agreement, intellectual property agreement, and information security policy

  • Access should be restricted to only what is necessary to perform job duties

  • No access may be granted earlier than the official employee start date

  • Access requests and rights modifications shall be documented in an access request ticket or email. No permissions shall be granted without approval from the system or data owner or management

  • Records of all permission and privilege changes shall be maintained for no less than one year

Management of Privileged Access

Granting of administrative rights shall be strictly controlled, and requires approval from the asset owner.

User Access Reviews

Administrators shall perform access rights reviews of user, administrator, and service accounts on a quarterly basis to verify that user access is limited to systems that are required for their job function. Access reviews shall be documented.

Access reviews may include group membership as well as evaluations of any specific or exception-based permission. Access rights shall also be reviewed as part of any job role change, including promotion, demotion, or transfer within the company.

Removal & Adjustment of Access Rights

The access rights of all users shall be promptly removed upon termination of their employment or contract, or when rights are no longer needed due to a change in job function or role. The maximum allowable time period for access termination is 24 business hours.

Access Provisioning, Deprovisioning, and Change Procedure

The Access Management Procedure for ecoPortal systems follows these steps:

Request Process:

1. Any individual requiring access or revocation to privileged information must submit a request or have a request submitted in writing to the designated personnel responsible for managing privileged information access.

2. The request should clearly outline the purpose and justification for accessing or revoking the access to the privileged information.

3. The request should also include the specific details of the information being requested if access is being granted, such as file names, database tables, or other relevant identifiers.

Approval and Authorization:

1. The request will be reviewed and approved by the designated personnel responsible for managing privileged information access.

2. The approval process may involve verifying the requester's need-to-know basis, ensuring compliance with relevant policies, and assessing potential risks associated with granting access.

3. Only authorized personnel with a legitimate business need will be granted access to the requested privileged information. All access will be granted based off the least privilege required.

4. The approval decision will be communicated to the requester in a timely manner.

Documentation:

1. All requests and approvals for privileged information access or revocation must be sufficiently documented/able to be provided for auditing purposes.

2. Any changes or updates to the access permissions should be properly recorded and documented.

User Responsibility for the Management of Secret Authentication Information

Control and management of individual user passwords is the responsibility of all ecoPortal personnel and third-party users. Users shall protect secret authentication information in accordance with the Information Security Policy.

Password Policy

Where feasible, passwords for confidential systems shall be configured for at least to be a minimum of 16 (sixteen) characters in length and are required to be changed at least every 6 (six) months. Password managers are strongly encouraged to be used.


System and Application Access

Information Access Restriction

Applications must restrict access to program functions and information to authorized users and support personnel in accordance with the defined access control policy. The level and type of restrictions applied by each application should be based on the individual application requirements, as identified by the data owner. The application-specific access control policy must also conform to ecoPortal policies regarding access controls and data management.

Prior to implementation, evaluation criteria are to be applied to application software to determine the necessary access controls and data policies. Assessment criteria include, but are not limited to:

  • Sensitivity and classification of data.

  • Risk to the organization of unauthorized access or disclosure of data

  • The ability to, and granularity of, control(s) on user access rights to the application and data stored within the application

  • Restrictions on data outputs, including filtering sensitive information, controlling output, and restricting information access to authorized personnel

  • Controls over access rights between the evaluated application and other applications and systems

  • Programmatic restrictions on user access to application functions and privileged instructions

  • Logging and auditing functionality for system functions and information access

  • Data retention and aging features

All unnecessary default accounts must be removed or disabled before making a system available on the network. Specifically, vendor default passwords and credentials must be changed on all ecoPortal systems, devices, and infrastructure prior to deployment. This applies to ALL default passwords, including but not limited to those used by operating systems, software that provides security services, application and system accounts, and Simple Network Management Protocol (SNMP) community strings where feasible.

Secure Log-on Procedures

Secure log-on controls shall be designed and selected in accordance with the sensitivity of data and the risk of unauthorized access based on the totality of the security and access control architecture.

Password Management System

Systems for managing passwords should be interactive and assist ecoPortal personnel in maintaining password standards by enforcing password strength criteria including minimum length, and password complexity where feasible.

All storage and transmission of passwords are to be protected using appropriate cryptographic protections, either through hashing or encryption.

Use of Privileged Utility Programs

Use of utility programs, system files, or other software that might be capable of overriding system and application controls or altering system configurations must be restricted to the minimum personnel required. Systems are to maintain logs of all use of system utilities or alteration of system configurations. Extraneous system utilities or other privileged programs are to be removed or disabled as part of the system build and configuration process.

Management approval is required prior to the installation or use of any ad hoc or third-party system utilities.

Access to Program Source Code

Access to program source code and associated items, including designs, specifications, verification plans, and validation plans shall be strictly controlled in order to prevent the introduction of unauthorized functionality into software, avoid unintentional changes, and protect ecoPortal intellectual property.

All-access to source code shall be based on business need and must be logged for review and audit.

Exceptions

Requests for an exception to this Policy must be submitted to the IT Manager for approval.

Violations & Enforcement

Any known violations of this policy should be reported to the IT Manager. Violations of this policy can result in immediate withdrawal or suspension of the system and network privileges and/or disciplinary action in accordance with company procedures up to and including termination of employment.