Measure from ISO 27001 Annex A |
Application* |
Reason for application or exclusion* |
A.5.1.1 |
Yes |
Role-specific guidelines enable effective interaction between all employees and external parties involved in ensuring information security. |
A.5.1.2 |
Yes |
Regular updates to the guides ensure that the latest developments and tasks are included and that the guides remain effective and appropriate. |
A.6.1.1 |
Yes |
Role assignments help us determine who has what responsibilities regarding information security measures in which situations. |
A.6.1.2 |
Yes |
We implement segregation of duties as far as possible to ensure that a system of mutual assurance is created for safety-critical tasks. However, it ends where it leads to inflexibility and cannot be achieved with the existing staffing levels. |
A.6.1.3 |
Yes |
Contacts with relevant authorities provide us with early information on vulnerabilities, threats and legislative developments that could be relevant to information security. |
A.6.1.4 |
Yes |
Contacts with relevant interest groups provide us with early information on vulnerabilities, threats, and other developments that could be relevant to information security. |
A.6.1.5 |
Yes |
By looking at planned information security requirements in our projects, we are able to control and implement them in a targeted manner and at an early stage. |
A.6.2.1 |
Yes |
Mobile devices are an easy gateway for attacks and security vulnerabilities. That’s why we regulate how they can and cannot be used. |
A.6.2.2 |
Yes |
Similar to mobile devices, teleworkplaces are not fully “controllable” and can be a gateway for attacks and security breaches. Therefore, we regulate how to work in telework in order to create security. |
A.7.1.1 |
Yes |
We rely on only hiring people who are capable of meeting our safety requirements. Therefore, we carefully review who we hire (or have work for us as freelancers). |
A.7.1.2 |
Yes |
Agreements on information security that employees must adhere to can only be reliably adhered to if all parties have insight into what has been agreed at all times. That’s why we rely on contractual arrangements here. |
A.7.2.1 |
Yes |
Information security is only taken seriously if the management stands behind it and demands compliance on a sustained basis. That’s why we hold management accountable. |
A.7.2.2 |
Yes |
To ensure that our employees are able to implement information security, we provide training in this area and develop each employee so that he or she can safely perform the tasks assigned to him or her with regard to information security. |
A.7.2.3 |
Yes |
If employees do not fulfill their information security duties, we care. We talk about it and point it out. This ensures that the importance of the issue is recognized. |
A.7.3.1 |
Yes |
Since we know that information security does not simply stop at the end of an employee’s employment, we ensure that we also regulate the obligations that exist beyond the end of working hours. |
A.8.1.1 |
Yes |
Devices (and other assets) can only be operated safely if they are covered. |
A.8.1.2 |
Yes |
Securing devices (and other assets) is only possible if someone feels responsible for each asset. Therefore, we ensure this. |
A.8.1.3 |
Yes |
Securing devices (and other assets) is only possible if it is clear for each device which use is permissible – i.e. “safe”. Therefore, we ensure that assets are only used safely. |
A.8.1.4 |
Yes |
To ensure that equipment is not left unattended when the employee responsible for it leaves the company, there is a duty to return it in a regulated manner. |
A.8.2.1 |
Yes |
Different types of information are critical in different ways. Therefore, we have classified the types of information that require protection in our company. |
A.8.2.2 |
Yes |
So that it is quickly clear to everyone which information is classified and how, these are marked. |
A.8.2.3 |
Yes |
To ensure that devices (and other assets) are handled as intended (and improper use does not inadvertently compromise information security), there are rules for how all major devices may be used. |
A.8.3.1 |
Yes |
Removable data carriers can be lost quickly. Therefore, we have regulated how and under what conditions they may be used. |
A.8.3.2 |
Yes |
When data media are disposed of, critical information may still be stored on them. We have therefore regulated how to dispose of them safely. |
A.8.3.3 |
Yes |
When critical information is stored on transportable data carriers, the risk of it being compromised is higher than on non-transportable data carriers. That is why we have strictly regulated transport. |
A.9.1.1 |
Yes |
We have an access control policy that regulates who can access which devices and information and for what reason. This ensures that access to devices and information is not arbitrary. |
A.9.1.2 |
Yes |
We secure access to our networks so that information flowing in them is not compromised or the networks themselves cannot meet our availability requirements due to excessive load. |
A.9.2.1 |
Yes |
To ensure that users are created and deleted correctly and cleanly, we have a process by which we register or deregister users. |
A.9.2.2 |
Yes |
To ensure that registered users are granted rights correctly and cleanly, we have a process by which we grant and revoke rights to users. |
A.9.2.3 |
Yes |
To ensure that privileged access (admin accounts) does not intentionally or unintentionally compromise information security, we restrict such access to only those individuals who need it. |
A.9.2.4 |
Yes |
We allocate secret authentication information (passwords, etc.) via a regulated process to ensure that it remains secret during allocation. |
A.9.2.5 |
Yes |
All employees who are responsible for devices (and other assets) at our company regularly check whether the access rights granted are still necessary. This is how we ensure that unauthorized persons no longer have access. |
A.9.2.6 |
Yes |
When employees (or freelancers who work for us) change their job responsibilities or leave us, we adjust or delete their access rights so that they do not have unauthorized access to sensitive information. |
A.9.3.1 |
Yes |
We oblige all users to keep their access data secret so that unauthorized persons cannot use them and thus gain access to information worthy of protection. |
A.9.4.1 |
Yes |
In accordance with the need-to-know principle, we restrict access to information to those employees who need to have access to this information in order to perform their duties – all others are not granted access. In this way, we ensure as far as possible that no one who does not actually need access to information worthy of protection inadvertently or deliberately handles it in an insecure manner. |
A.9.4.2 |
Yes |
To ensure that secret authentication information is not compromised after it is entered into information systems, we use only secure login procedures in which authentication information is transported securely. |
A.9.4.3 |
Yes |
To prevent passwords from being guessed or spied out via brute force, we ensure that they are secure (long enough, complex enough) via system-side and organizational guidelines. |
A.9.4.4 |
Yes |
We restrict the use of privileged utilities (“Run as…”) as much as possible, because these programs can be a gateway for attacks if malware can suddenly work with admin privileges. |
A.9.4.5 |
Yes |
Our source code repository is also a system to which we only grant access in accordance with our access control policy, so that no unauthorized persons can misuse or modify source code. |
A.10.1.1 |
Yes |
We have a policy to encrypt information – both when it is stored and when it is sent. This ensures that we protect critical information appropriately against spying. |
A.10.1.2 |
Yes |
We have a policy on the use of cryptographic keys, because encrypted and authenticated information is only as secure as the storage and use of its keys. |
A.11.1.1 |
Yes |
We have defined physical security zones at our company in which certain information security regulations apply. In this way, we ensure that security-critical information cannot be compromised on our premises. |
A.11.1.2 |
Yes |
We ensure that our security zones are protected in such a way that it is not possible to simply enter them without authorization. In this way, we improve the security of the information and devices in the zones. |
A.11.1.3 |
Yes |
We protect our offices, rooms and facilities so that no information worth protecting can be compromised here. |
A.11.1.4 |
Yes |
We take care of adequate protection against natural disasters, malicious attacks and robberies so that we do not lose any information worth protecting due to these incidents. |
A.11.1.5 |
Yes |
We have established procedures that apply to work in secure areas so that we do not unintentionally compromise the security of sensitive information here. |
A.11.1.6 |
Yes |
We have defined access points to our premises and monitor them to ensure that no unauthorized persons can enter at these points and compromise information security. |
A.11.2.1 |
Yes |
To ensure that important equipment and other operating resources do not fail, we make sure that they are set up safely. |
A.11.2.2 |
Yes |
We design and protect utility lines (power, water, etc.) so that failures and leaks do not happen if at all possible, or if they do, that they do not then compromise the security of the information requiring protection. |
A.11.2.3 |
Yes |
We protect data transmission lines to ensure that they are not interrupted or tapped, and thus that sensitive information is not compromised. |
A.11.2.4 |
Yes |
To ensure that equipment that is important for information security does not fail, we ensure that it is professionally maintained in accordance with the scheduled intervals. |
A.11.2.5 |
Yes |
Anyone who wants to remove devices or other assets from their intended locations must arrange this in advance. This ensures that we always know where important devices are and detect their loss early so that we can react. |
A.11.2.6 |
Yes |
When devices are removed (and operated away from their actual location), we have rules that specify how they must be secured so that sensitive information processed with them is not compromised. |
A.11.2.7 |
Yes |
We erase devices that contain storage media before we dispose of or recycle them. In this way, we ensure that no information requiring protection (including copyright protection) is stored on them. |
A.11.2.8 |
Yes |
To prevent unauthorized persons from gaining access to unattended devices that are important for information security, we protect such devices in an appropriate manner when they are not being observed by employees: By locking them away, by locking them up, and by other appropriate measures. |
A.11.2.9 |
Yes |
To ensure that sensitive information cannot be compromised among employees, we have a “clean desk policy”. |
A.12.1.1 |
Yes |
If information security depends on operating procedures on devices or systems being followed precisely, then we document these operating procedures. |
A.12.1.2 |
Yes |
We ensure that important processes, information systems or the like are not changed “just like that” because this can jeopardize information security. |
A.12.1.3 |
Yes |
If the utilization of certain resources (systems, employees) are important for information security, we monitor them in order to identify trends towards overload at an early stage and to be able to counteract them. |
A.12.1.4 |
Yes |
We deliberately separate development, staging and production systems so that changes to one cannot have unexpected consequences on the information security of the other. |
A.12.2.1 |
Yes |
We implement anti-malware measures on all systems where reasonably possible to ensure that systems are hardened against malicious attacks and maintain information security. |
A.12.3.1 |
Yes |
To ensure that important information is not lost, we have a backup policy for all information whose availability requires protection. |
A.12.4.1 |
Yes |
In order to be able to evaluate, either in advance or forensically, which events affect our systems, we log all important events. |
A.12.4.2 |
Yes |
The log information is in turn secured so that it cannot be falsified, deleted or disclosed, either consciously or unconsciously. |
A.12.4.3 |
Yes |
The same applies to log information resulting from admin activities. |
A.12.4.4 |
Yes |
In order to correctly use log information for analysis, we synchronize the clocks of all systems that generate log information. |
A.12.5.1 |
Yes |
To ensure that critical information systems do not abruptly fail or fail to work as required, we make sure that new or modified software is not installed on them just like that. |
A.12.6.1 |
Yes |
We obtain information about technical vulnerabilities in the systems we use so that we can remedy them quickly and prevent sensitive information from being compromised. |
A.12.6.2 |
Yes |
An installation policy implemented on the software side and in the organization ensures that the risk of unknowingly installing malware is reduced. |
A.12.7.1 |
Yes |
If our production systems are to be audited, we will ensure that this does not happen during peak business hours so that we can also ensure the availability of our systems for our customers during the audit. |
A.13.1.1 |
Yes |
We design and manage the networks used by our systems so that they do not fail abruptly or cannot handle the expected traffic. |
A.13.1.2 |
Yes |
We consider what network performance we need (both internally and externally) and ensure that it is available so as not to be surprised. |
A.13.1.3 |
Yes |
We separate, where necessary, those networks in which our employees work and those networks in which our productive systems operate so that they cannot interfere with each other. |
A.13.2.1 |
Yes |
To ensure that employees know how to protect which information when they transfer it, we have established transfer guidelines that can be referred to at any time. |
A.13.2.2 |
Yes |
We enter into agreements with our partners on how critical business information is transferred so that it is adequately protected during transfer. |
A.13.2.3 |
Yes |
We also secure sensitive information when we send it in electronic messages. We do this because the rapid exchange of information via messages/chats is important to us and is widely used – which is precisely why it needs to be secure. |
A.13.2.4 |
Yes |
Our non-disclosure agreements are always up to date to ensure that we always keep what is important to us secret and up to date. |
A.14.1.1 |
Yes |
We analyze what information security requirements we have for the systems we develop (or buy in) so that we can implement them. |
A.14.1.2 |
Yes |
We protect our online systems so that they are safe from fraudulent attacks that cause us to be unable to honor our contracts with our customers. |
A.14.1.3 |
Yes |
We protect all transactions that our customers make with our applications so that they remain complete, unaltered, authentic, and confidential. |
A.14.2.1 |
Yes |
We have a software development policy and require everyone who develops software for us to apply it so that software is developed safely. |
A.14.2.2 |
Yes |
We don’t change the systems we use to develop software or the software products we develop “just like that”, but only after thoroughly testing what we change – because we know that changes can also mean information security leaks. And we want to avoid that. |
A.14.2.3 |
Yes |
When we update the operating systems used in development, we check that our development systems still function error-free afterwards – because we know that not being error-free can lead to information security leaks. |
A.14.2.4 |
Yes |
We update software packages not “because we can”, but because we see the need. We test the new packages in advance. |
A.14.2.5 |
Yes |
We have principles for the development of safe systems. We apply these to ensure that the systems we develop are also safe. |
A.14.2.6 |
Yes |
Since security risks can also be introduced into developed systems via development environments, we ensure that we secure the development environments we use as well as possible. |
A.14.2.7 |
Yes |
We outsource development activities to partners. We monitor these because we want to ensure that the systems developed there are as secure as we need them to be. |
A.14.2.8 |
Yes |
We test all the safety functions of the systems we develop so that we are sure they work as intended. |
A.14.2.9 |
Yes |
We also conduct acceptance tests for all systems we purchase or develop so that we can ensure that their security functions work not only in individual cases, but also in the overall context. |
A.14.3.1 |
Yes |
Since we know that test data sometimes comes from production databases, we make sure that our test data is carefully protected. |
A.15.1.1 |
Yes |
If our service providers need to access our organization’s assets, we regulate this in advance to ensure that no security gaps occur. |
A.15.1.2 |
Yes |
We conclude contracts with all service providers relevant for information security that contain the obligations of the service providers with regard to information security. |
A.15.1.3 |
Yes |
In the contracts, we include provisions relating to information security risks that occur or may occur at service providers because we want to avoid information security risks even if they occur at our service providers. |
A.15.2.1 |
Yes |
We continuously check whether our service providers adhere to the information security regulations agreed with them so that we can be sure about this. |
A.15.2.2 |
Yes |
Services provided by our suppliers may change: we keep this in mind so that we can adjust the information security arrangements in the case with our service providers. |
A.16.1.1 |
Yes |
We have established a procedure that enables us to respond quickly and reliably to information security incidents. This is important to us in order to be able to clarify information security incidents quickly. |
A.16.1.2 |
Yes |
We ensure that information security events and incidents are reported and handled as quickly as possible through the above procedures, as this ensures that we restore security as quickly as possible if it does become compromised. |
A.16.1.3 |
Yes |
We encourage our employees and service providers to report information security incidents and events promptly so that we can address them quickly and effectively. |
A.16.1.4 |
Yes |
We evaluate each information security event (i.e., any suspicion that the targeted information security has been compromised) to determine whether it is an incident (i.e., security has been demonstrably compromised) in order to respond adequately. |
A.16.1.5 |
Yes |
We ensure that we respond adequately to identified information security incidents so that they are remediated as quickly as possible. |
A.16.1.6 |
Yes |
We ensure that we specifically learn from previous information security incidents so that they do not occur again in the future, if possible. |
A.16.1.7 |
Yes |
In the event of acute information security incidents, all employees and also service providers are required to collect evidence to facilitate the assessment of the incident or to be able to reconstruct it later. |
A.17.1.1 |
Yes |
We have determined in which exceptional situations we want to maintain which level of information security so that we can communicate this to our interested parties and especially contractors and focus on maintaining the defined information security. |
A.17.1.2 |
Yes |
We establish procedures to ensure information security in the defined exceptional situations so that we can respond when necessary. |
A.17.1.3 |
Yes |
We test the above procedures to make sure they work when we need them to. |
A.17.2.1 |
Yes |
We plan the infrastructure we need in such a redundant way that the risks arising from failure can be reduced to an acceptable level. |
A.18.1.1 |
Yes |
We collect all legal, contractual and regulatory regulations applicable to us that relate to information security so that we know which requirements we need to meet from this perspective. |
A.18.1.2 |
Yes |
We have procedures in place to ensure that we use copyrighted works as intended or in accordance with the contract. |
A.18.1.3 |
Yes |
We store documents as required by applicable laws, contracts and other regulatory requirements, so that information security in this area is taken into account. |
A.18.1.4 |
Yes |
We comply with the DSGVO with regard to personal data. |
A.18.1.5 |
Yes |
We adhere to all legal cryptography regulations that apply to us – both minimum and maximum allowed cryptography, in order to be able to consistently ensure the legally compliant operation of our software products. |
A.18.2.1 |
Yes |
We have our information security arrangements reviewed by independent external bodies (e.g., certification organizations) to ensure that we do not overlook anything important. |
A.18.2.2 |
Yes |
We check internally whether all our employees also adhere to the specified regulations on information security so that they do not just pay lip service to them. |
A.18.2.3 |
Yes |
We also review the information systems we use to ensure that they comply with all security policies so that information security leaks do not inadvertently occur here. |