Statement of Applicability
Our Statement of Applicability (SoA) outlines the specific ISO 27001 controls relevant to Aha! and provides transparent insights into the controls we were audited against as a part of our certification. This rigorous process ensures that our information security measures align with internationally recognized standards and demonstrates our unwavering commitment to safeguarding your data and upholding your trust.
Our ISO27001 Certificate and Statement of Applicability are available here:
Aha! Labs ISO27001 Certificate (Public)
Aha! Labs ISO27001 Statement of Applicability (Public)
Aha! implements the following technical and organizational security measures:
5 Information Security Policies | 5.1 Management direction for Information Security | ||
5.1.1 | Policies for information security | A set of policies for information security shall be defined, approved by management, published and communicated to employees and relevant external parties. | |
5.1.2 | Review of the policies for Information Security | The policies for information security shall be reviewed at planned intervals or if significant changes occur to ensure their continuing suitability, adequacy and effectiveness. | |
6 Organization of Information Security | 6.1 Internal organization | ||
6.1.1 | Information Security roles and responsibilities | All information security responsibilities shall be defined and allocated. | |
6.1.2 | Segregation of duties | Conflicting duties and areas of responsibility shall be segregated to reduce opportunities for unauthorized or unintentional modification or misuse of Aha! assets. | |
6.1.3 | Contact with authorities | Appropriate contacts with relevant authorities shall be maintained. | |
6.1.4 | Contact with special interest groups | Appropriate contacts with special interest groups or other specialist security forums and professional associations shall be maintained. | |
6.1.5 | Information Security in project management | Information security shall be addressed in project management, regardless of the type of project. | |
6.2 Mobile devices and teleworking | |||
6.2.1 | Mobile device policy | A policy and supporting security measures shall be adopted to manage the risks introduced by using mobile devices. | |
6.2.2 | Teleworking | A policy and supporting security measures shall be implemented to protect information accessed, processed or stored at teleworking sites. | |
7 Human Resource Security | 7.1 Prior to employment | ||
7.1.1 | Screening | Background verification checks on all candidates for employment shall be carried out in accordance with relevant laws, regulations and ethics and shall be proportional to the business requirements, the classification of the information to be accessed and the perceived risks. | |
7.1.2 | Terms and conditions of employment | The contractual agreements with employees and contractors shall state their and Aha! responsibilities for information security. | |
7.2 During employment | |||
7.2.1 | Management responsibilities | Management shall require all employees and contractors to apply information security in accordance with the established policies and procedures. | |
7.2.2 | Information Security awareness, education and training | All employees of Aha! and, where relevant, contractors shall receive appropriate awareness education and training and regular updates in Aha! policies and procedures, as relevant for their job function. | |
7.2.3 | Disciplinary process | There shall be a formal and communicated disciplinary process in place to take action against employees who have committed an information security breach | |
7.3 Termination and change of employment | |||
7.3.1 | Termination or change of employment responsibilities | Information security responsibilities and duties that remain valid after termination or change of employment shall be defined, communicated to the employee or contractor and enforced. | |
8 Asset Management | 8.1 Responsibility for Assets | ||
8.1.1 | Inventory of assets | Assets associated with information and information processing facilities shall be identified and an inventory of these assets shall be drawn up and maintained. | |
8.1.2 | Ownership of assets | Assets maintained in the inventory shall be owned. | |
8.1.3 | Acceptable use of assets | Rules for the acceptable use of information and of assets associated with information and information processing facilities shall be identified, documented and implemented. | |
8.1.4 | Return of assets | All employees and external party users shall return all Aha! assets upon termination of their employment, contract or agreement. | |
8.2 Information Classification | |||
8.2.1 | Classification of information | Information shall be classified in terms of legal requirements, value, criticality and sensitivity to unauthorized disclosure or modification. | |
8.2.2 | Labelling of information | An appropriate set of procedures for information labelling shall be developed and implemented in accordance with the Aha! information classification scheme. | |
8.2.3 | Handling of assets | Procedures for handling assets shall be developed and implemented in accordance with the information classification scheme adopted by the organization. | |
8.3 Media handling | |||
8.3.1 | Management of removable media | Procedures shall be implemented for the management of removable media in accordance with the classification scheme adopted by the organization. | |
8.3.2 | Disposal of media | Media shall be disposed of securely when no longer required, using formal procedures. | |
8.3.3 | Physical media transfer | Media containing information shall be protected against unauthorized access, misuse or corruption during transportation. | |
9 Access Control | 9.1 Business requirements of access control | ||
9.1.1 | Access control policy | An access control policy shall be established, documented and reviewed based on business and information security requirements. | |
9.1.2 | Access to networks and network services | Users shall only be provided with access to the network and network services that they have been specifically authorized to use. | |
9.2 User access management | |||
9.2.1 | User registration and de-registration | A formal user registration and de-registration process shall be implemented to enable assignment of access rights. | |
9.2.2 | User access provisioning | A formal user access provisioning process shall be implemented to assign or revoke access rights for all user types to all systems and services. | |
9.2.3 | Management of privileged access rights | The allocation and use of privileged access rights shall be restricted and controlled. | |
9.2.4 | Management of secret authentication information of users | The allocation of secret authentication information shall be con- trolled through a formal management process. | |
9.2.5 | Review of user access rights | Asset owners shall review users’ access rights at regular intervals. | |
9.2.6 | Removal or adjustment of access rights | The access rights of all employees and external party users to information and information processing facilities shall be removed upon termination of their employment, contract or agreement, or adjusted upon change. | |
9.3 User responsibilities | |||
9.3.1 | Use of secret authentication information | Users shall be required to follow Aha! practices in the use of secret authentication information. | |
9.4 System and application access control | |||
9.4.1 | Information access restriction | Access to information and application system functions shall be restricted in accordance with the access control policy. | |
9.4.2 | Secure log-on procedures | Where required by the access control policy, access to systems and applications shall be controlled by a secure log-on procedure. | |
9.4.3 | Password management system | Password management systems shall be interactive and shall ensure quality passwords. | |
9.4.4 | Use of privileged utility programs | The use of utility programs that might be capable of overriding system and application controls shall be restricted and tightly controlled. | |
9.4.5 | Access control to program source code | Access to program source code shall be restricted. | |
10 Cryptography | 10.1 Cryptographic controls | ||
10.1.1 | Policy on the use of cryptographic controls | A policy on the use of cryptographic controls for protection of information shall be developed and implemented. | |
10.1.2 | Key management | A policy on the use, protection and lifetime of cryptographic keys shall be developed and implemented through their whole lifecycle | |
12 Operations Security | 12.1 Operational procedures and responsibilities | ||
12.1.1 | Documented operating procedures | Operating procedures shall be documented and made available to all users who need them. | |
12.1.2 | Change management | Changes to Aha! business processes, information processing facilities and systems that affect information security shall be controlled. | |
12.1.3 | Capacity management | The use of resources shall be monitored, tuned and projections made of future capacity requirements to ensure the required system performance. | |
12.1.4 | Separation of development, testing and operational environments | Development, testing, and operational environments shall be separated to reduce the risks of unauthorized access or changes to the operational environment. | |
12.2 Protection from malware | |||
12.2.1 | Controls against malware | Detection, prevention and recovery controls to protect against malware shall be implemented, combined with appropriate user awareness. | |
12.3 Backup | |||
12.3.1 | Information backup | Backup copies of information, software and system images shall be taken and tested regularly in accordance with an agreed backup policy. | |
12.4 Logging and monitoring | |||
12.4.1 | Event logging | Event logs recording user activities, exceptions, faults and infor- mation security events shall be produced, kept and regularly reviewed. | |
12.4.2 | Protection of log information | Logging facilities and log information shall be protected against tampering and unauthorized access. | |
12.4.3 | Administrator and operator logs | System administrator and system operator activities shall be logged and the logs protected and regularly reviewed. | |
12.4.4 | Clock synchronization | The clocks of all relevant information processing systems within an organization or security domain shall be synchronized to a single reference time source. | |
12.5 Control of operational software | |||
12.5.1 | Installation of software on operational systems | Procedures shall be implemented to control the installation of soft- ware on operational systems. | |
12.6 Technical vulnerability management | |||
12.6.1 | Management of technical vulnerabilities | Information about technical vulnerabilities of information systems being used shall be obtained in a timely fashion, the organization’s exposure to such vulnerabilities evaluated and appropriate measures taken to address the associated risk. | |
12.6.2 | Restrictions on software installation | Rules governing the installation of software by users shall be established and implemented. | |
12.7 Information systems audit considerations | |||
12.7.1 | Information systems audit controls | Audit requirements and activities involving verification of operational systems shall be carefully planned and agreed to minimize disruptions to business processes. | |
13 Communications Security | 13.1 Network security management | ||
13.1.1 | Network controls | Networks shall be managed and controlled to protect information in systems and applications. | |
13.1.2 | Security of network services | Security mechanisms, service levels and management requirements of all network services shall be identified and included in network services agreements, whether these services are provided in-house or outsourced. | |
13.1.3 | Segregation in networks | Groups of information services, users and information systems shall be segregated on networks. | |
13.2 Information transfer | |||
13.2.1 | Information transfer policies and procedures | Formal transfer policies, procedures and controls shall be in place to protect the transfer of information through the use of all types of communication facilities. | |
13.2.2 | Agreements on information transfer | Agreements shall address the secure transfer of business information between Aha! and external parties. | |
13.2.3 | Electronic messaging | Information involved in electronic messaging shall be appropriately protected. | |
13.2.4 | Confidentiality or non-disclosure agreements | Requirements for confidentiality or non-disclosure agreements reflecting the organization’s needs for the protection of information shall be identified, regularly reviewed and documented. | |
14 System Acquisition, Development and Maintenance | 14.1 Security requirements of information systems | ||
14.1.1 | Information Security requirements analysis and specification | The information security related requirements shall be included in the requirements for new information systems or enhancements to existing information systems. | |
14.1.2 | Securing applications services on public networks | Information involved in application services passing over public networks shall be protected from fraudulent activity, contract dis- pute and unauthorized disclosure and modification. | |
14.1.3 | Protecting application services transactions | Information involved in application service transactions shall be protected to prevent incomplete transmission, mis-routing, unau- thorized message alteration, unauthorized disclosure, unauthor- ized message duplication or replay. | |
14.2 Security in development and support processes | |||
14.2.1 | Secure development policy | Rules for the development of software and systems shall be established and applied to developments within the organization. | |
14.2.2 | System change control procedures | Changes to systems within the development lifecycle shall be con- trolled by the use of formal change control procedures. | |
14.2.3 | Technical review of applications after operating platform changes | When operating platforms are changed, business critical applications shall be reviewed and tested to ensure there is no adverse impact on Aha! operations or security. | |
14.2.4 | Restrictions on changes to software packages | Modifications to software packages shall be discouraged, limited to necessary changes and all changes shall be strictly controlled. | |
14.2.5 | Secure system engineering principles | Principles for engineering secure systems shall be established, documented, maintained and applied to any information system implementation efforts. | |
14.2.6 | Secure development environment | Organizations shall establish and appropriately protect secure development environments for system development and integration efforts that cover the entire system development lifecycle. | |
14.2.8 | System security testing | Testing of security functionality shall be carried out during development. | |
14.2.9 | System acceptance testing | Acceptance testing programs and related criteria shall be established for new information systems, upgrades and new versions. | |
14.3 Test data | |||
14.3.1 | Protection of test data | Test data shall be selected carefully, protected and controlled. | |
15 Supplier Relationships | 15.1 Information Security in supplier relationships | ||
15.1.1 | Information Security policy for supplier relationships | Information security requirements for mitigating the risks associated with supplier’s access to the organization’s assets shall be agreed with the supplier and documented. | |
15.1.2 | Addressing security within supplier agreements | All relevant information security requirements shall be established and agreed with each supplier that may access, process, store, communicate, or provide IT infrastructure components for, the organization’s information. | |
15.1.3 | Information and communication technology supply chain | Agreements with suppliers shall include requirements to address the information security risks associated with information and communications technology services and product supply chain. | |
15.2 Supplier service delivery management | |||
15.2.1 | Monitoring and review of supplier services | Organizations shall regularly monitor, review and audit supplier service delivery. | |
15.2.2 | Managing changes to supplier services | Changes to the provision of services by suppliers, including maintaining and improving existing information security policies, procedures and controls, shall be managed, taking account of the criticality of business information, systems and processes involved and re-assessment of risks. | |
16 Information Security Incident Management | 16.1 Management of Information Security incidents and improvements | ||
16.1.1 | Responsibilities and procedures | Management responsibilities and procedures shall be established to ensure a quick, effective and orderly response to information security incidents. | |
16.1.2 | Reporting Information Security events | Information security events shall be reported through appropriate management channels as quickly as possible. | |
16.1.3 | Reporting Information Security weaknesses | Employees and contractors using Aha! information systems and services shall be required to note and report any observed or suspected information security weaknesses in systems or services. | |
16.1.4 | Assessment of and decision on Information Security events | Information security events shall be assessed and it shall be decided if they are to be classified as information security incidents. | |
16.1.5 | Response to Information Security incidents | Information security incidents shall be responded to in accordance with the documented procedures. | |
16.1.6 | Learning from Information Security incidents | Knowledge gained from analyzing and resolving information security incidents shall be used to reduce the likelihood or impact of future incidents. | |
16.1.7 | Collection of evidence | The organization shall define and apply procedures for the identification, collection, acquisition and preservation of information, which can serve as evidence. | |
17 Information Security aspects of Business Continuity Management | 17.1 Information Security continuity | ||
17.1.1 | Planning Information Security continuity | The organization shall determine its requirements for information security and the continuity of information security management in adverse situations, e.g. during a crisis or disaster. | |
17.1.2 | Implementing Information Security continuity | The organization shall establish, document, implement and main- tain processes, procedures and controls to ensure the required level of continuity for information security during an adverse situa- tion. | |
17.1.3 | Verify, review and evaluate Information Security continuity | The organization shall verify the established and implemented information security continuity controls at regular intervals in order to ensure that they are valid and effective during adverse situations. | |
17.2 Redundancies | |||
17.2.1 | Availability of information processing facilities | Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements. | |
18 Compliance | 18.1 Compliance with legal and contractual requirements | ||
18.1.1 | Identification of applicable legislation and contractual requirements | All relevant legislative statutory, regulatory, contractual requirements and the organization’s approach to meet these requirements shall be explicitly identified, documented and kept up to date for each information system and the organization. | |
18.1.2 | Intellectual property rights | Appropriate procedures shall be implemented to ensure compliance with legislative, regulatory and contractual requirements related to intellectual property rights and use of proprietary software products. | |
18.1.3 | Protection | Records shall be protected from loss, destruction, falsification, unauthorized access and unauthorized release, in accordance with legislatory, regulatory, contractual and business requirements. | |
18.1.4 | Privacy and protection of personally identifiable information | Privacy and protection of personally identifiable information shall be ensured as required in relevant legislation and regulation where applicable. | |
18.1.5 | Regulation of cryptographic controls | Cryptographic controls shall be used in compliance with all relevant agreements, legislation and regulations. | |
18.2 Information Security reviews | |||
18.2.1 | Independent review of Information Security | The organization’s approach to managing information security and its implementation (i.e. control objectives, controls, policies, processes and procedures for information security) shall be reviewed independently at planned intervals or when significant changes occur. | |
18.2.2 | Compliance with security policies and standards | Managers shall regularly review the compliance of information processing and procedures within their area of responsibility with the appropriate security policies, standards and any other security requirements. | |
18.2.3 | Technical compliance review | Information systems shall be regularly reviewed for compliance with Aha! information security policies and standards. | |
