Search is not available for this dataset
index int64 | Label string | Identifier string | Description string |
|---|---|---|---|
1 | Office Products | APP.1.1 | Target Object: Application / Order: R2 |
2 | Regulations for Software Development by End Users (S) | APP.1.1.A10 | For software development based on Office applications (e.g. with macros), binding regulations SHOULD be established (see also APP.1.1.A2 Limiting Active Content). First, every organisation SHOULD make a policy decision as to whether or not it wants to allow in-house development of this kind by end users at all. The dec... |
3 | Controlled Use of Extensions for Office Products (S) | APP.1.1.A11 | All add-ons and extensions for Office products SHOULD be tested in the same way as new versions prior to productive use. This testing SHOULD only be carried out on isolated test systems. The tests SHOULD check if the extensions have any adverse effects on the Office products and IT systems in operation. The tests of th... |
4 | No Cloud Storage [User] (S) | APP.1.1.A12 | The cloud storage features integrated into some Office products SHOULD be disabled as a matter of principle. All cloud drives SHOULD be disabled. All documents SHOULD be stored by users on file servers centrally managed by the organisation. Specialised applications SHOULD be used to share documents with third parties. ... |
5 | Use of Viewer Features [User] (S) | APP.1.1.A13 | Data from potentially unsafe sources SHOULD be automatically opened in a protected mode. Users SHOULD NOT be allowed to disable this feature. A list of trustworthy places from which content can be opened and edited directly SHOULD be defined. In the protected mode, it SHOULD NOT be possible to edit data directly. Activ... |
6 | Protection Against Subsequent Changes to Documents [User] (S) | APP.1.1.A14 | Depending on their intended use, documents SHOULD be suitably protected against subsequent modification. |
7 | Use of Encryption and Digital Signatures (H) | APP.1.1.A15 | Data that requires increased protection SHOULD only be stored and transmitted in encrypted form. Before using an encryption method integrated into an Office product, it SHOULD be checked to ensure that it offers sufficient protection. In addition, a process SHOULD be used that supports the digital signing of macros and... |
8 | Checking Document Integrity (H) | APP.1.1.A16 | When storing or transmitting data that requires increased protection, appropriate integrity checks SHOULD be used. Cryptographic procedures SHOULD also be used for data that requires protection against manipulation. |
9 | Awareness of Specific Office Properties (B) | APP.1.1.A17 | Appropriate efforts MUST be taken to make all users aware of the threat posed by active content. Appropriate efforts MUST also be taken to make all users aware of how documents from external sources are to be handled. Users SHOULD be informed about the capabilities and limits of the security functions of the software e... |
10 | Limiting Active Content (B) | APP.1.1.A2 | The automatic execution of embedded active content MUST be deactivated. If it is nevertheless necessary to run active content, care MUST be taken to ensure that active content is only run when it comes from trusted sources. All users MUST be instructed about features that restrict active content. |
11 | Secure Opening of Documents from External Sources [User] (B) | APP.1.1.A3 | All documents obtained from external sources MUST be scanned for malware before they are opened. All file formats considered problematic and those not required within an organisation MUST be prohibited. They SHOULD be blocked if possible. Technical safeguards SHOULD be implemented to enforce the scanning of documents f... |
12 | Testing New Versions of Office Products (S) | APP.1.1.A6 | New versions of Office products SHOULD be tested for compatibility with established tools such as macros, document templates, or organisation forms prior to productive use (see OPS.1.1.6 Software Testing and Approval). It SHOULD be ensured that important tools will continue to function as they should with each new soft... |
13 | Web Browsers | APP.1.2 | Target Object: Application / Order: R2 |
14 | Use of Basic Security Mechanisms (B) | APP.1.2.A1 | The web browser used MUST ensure that every instance and process can only access its own resources (sandboxing). Web pages MUST be isolated from each other in independent processes, or at least in their own threads. Plug-ins and extensions MUST also be executed in isolated areas. The web browser used MUST implement the... |
15 | Using the Private Mode [User] (H) | APP.1.2.A10 | In case of increased requirements regarding confidentiality, a web browser SHOULD be run in private mode so that no information or content will be stored permanently on the user's IT system. The browser SHOULD be configured so that local content will be deleted once the browser is closed. |
16 | Checking for Malicious Content (H) | APP.1.2.A11 | The web browser SHOULD check the Internet addresses accessed by the user for potentially malicious content. The web browser SHOULD warn the user if information on malicious content is present. It SHOULD NOT be possible to establish a connection that is classified as malicious. The procedure used for checking MUST NOT i... |
17 | Two-Browser Strategy (H) | APP.1.2.A12 | If the web browser in use has unresolved security problems, an alternative browser with a different platform SHOULD be installed as a fallback option for the user. |
18 | Use of DNS over HTTPS (B) | APP.1.2.A13 | An organisation MUST check whether the browsers in use employ DNS-over-HTTPS (DoH). Whether or not the function should be used MUST be specified. If the organisation uses DNS servers as resolvers that are accessed over untrusted networks, DoH SHOULD be used. If DoH is used, the organisation MUST specify a trusted DoH s... |
19 | Support for Secure Communication Encryption (B) | APP.1.2.A2 | The web browser MUST support a secure version of Transport Layer Security (TLS). Connections to web servers MUST be encrypted with TLS whenever this is supported by the web server in question. Insecure versions of TLS SHOULD be deactivated. The web browser MUST support and implement the HTTP Strict Transport Security (... |
20 | Use of Trusted Certificates (B) | APP.1.2.A3 | If a web browser provides its own list of trusted root certificates, it MUST be ensured that only administrators can change them. If this is not possible through technical safeguards, users MUST be prohibited from changing this list. It MUST also be ensured that the web browser can revoke certificates locally. The web ... |
21 | Password Management in Web Browsers (B) | APP.1.2.A6 | If a password manager is used in a web browser, it MUST create a direct and unique relationship between each web page and the password stored for it. The stored passwords MUST be encrypted. It MUST be ensured that the passwords stored in the password manager can only be accessed after entering a master password. Furthe... |
22 | Data Economy in Web Browsers [User] (S) | APP.1.2.A7 | Cookies from third parties SHOULD be refused in web browsers. It SHOULD be possible for users to delete stored cookies. The auto-complete function for data SHOULD be deactivated. If this function is nevertheless used, the user SHOULD be able to delete the corresponding data. The user SHOULD also be able to delete the w... |
23 | Using an Isolated Web Browser Environment (H) | APP.1.2.A9 | In case of increased protection needs, web browsers SHOULD be used that run in an isolated environment such as ReCoBS or on dedicated IT systems. |
24 | Mobile Applications (Apps) | APP.1.4 | Target Object: Application / Order: R2 |
25 | Requirements Analysis for the Use of Apps [Process Owner] (B) | APP.1.4.A1 | During requirements analysis, risks arising from mobile use in particular MUST be considered. The organisation MUST verify that its ability to check and influence the operating system environment of mobile devices is sufficient to facilitate their secure use. |
26 | Secure App Removal (S) | APP.1.4.A12 | When an app is uninstalled, the data it has stored on external systems (such as those operated by the app provider) SHOULD also be deleted. |
27 | Support for Additional Authentication Features for Apps (H) | APP.1.4.A14 | Whenever possible, a second factor SHOULD be employed for user authentication in apps. Here, it SHOULD be ensured that any required sensors or interfaces are present in all the devices used. In addition, biometric procedures SHOULD take into account how resistant the corresponding authentication is to possible forgery ... |
28 | Performing Penetration Tests for Apps (H) | APP.1.4.A15 | Before an app is approved for use, a penetration test SHOULD be performed. All communication interfaces to back-end systems, as well as the local storage of data, SHOULD be examined for possible vulnerabilities. The penetration tests SHOULD be repeated regularly and when major changes are made to the app. |
29 | Mobile Application Management (H) | APP.1.4.A16 | Whenever possible, a mobile application management solution SHOULD be used for the central configuration of business apps. |
30 | Distributing Sensitive Apps (S) | APP.1.4.A3 | Apps developed within an organisation and apps that process sensitive information SHOULD be distributed through the organisation's own app store or MDM solution. |
31 | Minimising and Checking App Authorisations [Process Owner] (B) | APP.1.4.A5 | Security-relevant authorisation settings MUST be established so that they cannot be changed by users or apps. If this is not technically possible, the authorisation settings MUST be regularly checked and reset. Before an app is introduced in an organisation, it MUST be ensured that it only has the minimum app authorisa... |
32 | Secure Storage of Local App Data (B) | APP.1.4.A7 | If apps can access an organisation's internal documents, it MUST be ensured that the local data storage of the app is adequately secured. In particular, access keys MUST be stored in an encrypted form. In addition, a mobile device's operating system MUST NOT be allowed to cache confidential data in other locations. |
33 | Preventing Data Leaks (B) | APP.1.4.A8 | To prevent unintended instances of apps transmitting confidential data or this data being used to create profiles of users, app communication MUST be appropriately restricted. To this end, communication SHOULD be analysed as part of the testing and approval procedure. Checks SHOULD also be carried out to determine whet... |
34 | General Directory Service | APP.2.1 | Target Object: Application / Order: R2 |
35 | Creation of a Security Policy for Directory Services (B) | APP.2.1.A1 | A security policy for the directory service MUST be drawn up. This policy SHOULD be in agreement with the organisation’s overall security concept. |
36 | Setting Up Access to Directory Services (S) | APP.2.1.A11 | Access to a directory service SHOULD be configured according to the security policy at hand. If the directory service is used as a server on the Internet, it SHOULD be protected accordingly by a security gateway. If anonymous users are to be granted extended access rights to individual sub-areas of the directory tree, ... |
37 | Monitoring Directory Services (S) | APP.2.1.A12 | Directory services SHOULD be monitored and logged together with the server on which they are running. |
38 | Protection of Communications with Directory Services (S) | APP.2.1.A13 | All communications with a directory service SHOULD be encrypted using SSL/TLS. The communication endpoint of the directory service server SHOULD NOT be reachable from the Internet. Exchanges of data between clients and the directory service server SHOULD be secured. The data that may be accessed SHOULD be defined. To p... |
39 | Orderly Decommissioning of a Directory Service [Process Owner] (S) | APP.2.1.A14 | When decommissioning a directory service, it SHOULD be ensured that the required rights and information continue to be sufficiently available. All other rights and information SHOULD be deleted. Furthermore, the users affected SHOULD be informed when a directory service is being decommissioned. When decommissioning ind... |
40 | Migration of Directory Services (S) | APP.2.1.A15 | In the event of a scheduled migration of directory services, a migration concept SHOULD be drawn up beforehand. The changes that have been made to a directory service scheme SHOULD be documented. Any extensive authorisations that were used to perform the directory service migration SHOULD be reset. The access rights fo... |
41 | Creation of a Business Continuity Plan for Directory Service Failure (H) | APP.2.1.A16 | Within the framework of contingency planning, there SHOULD be a need-based business continuity plan for directory services. Business continuity plans SHOULD be in place in case important directory service systems fail. All contingency procedures for the overall system configuration of directory service components SHOUL... |
42 | Planning the Use of Directory Services [Data Protection Officer, Process Owner] (B) | APP.2.1.A2 | The use of directory services MUST be planned carefully. The specific use of the directory service MUST be defined. It MUST be ensured that the directory service and all applications using it are compatible. In addition, a model consisting of object classes and attribute types MUST be developed that meets the requireme... |
43 | Setting Up Access Authorisations for Directory Services [Process Owner] (B) | APP.2.1.A3 | The tasks pertaining to the administration of the directory service itself and to the actual data administration MUST be clearly separated. The administrative tasks SHOULD be delegated such that overlap is avoided whenever possible. All administrative task areas and authorisations SHOULD be sufficiently documented. The... |
44 | Secure Installation of Directory Services (B) | APP.2.1.A4 | An installation concept MUST be drawn up in which administration and access authorisations will already be configured when installing the directory service. |
45 | Secure Configuration and Configuration Changes in Directory Services (B) | APP.2.1.A5 | The directory service MUST be configured securely. In addition to the server, the clients (IT systems and programs) MUST be included in the secure configuration of a directory service infrastructure. If the configuration of the connected IT systems is to be changed, users SHOULD be informed in good time about the corre... |
46 | Secure Operation of Directory Services (B) | APP.2.1.A6 | The security of the directory service MUST be maintained constantly during operation. All policies, regulations, and processes related to the operation of a directory service system SHOULD be documented. The workstations of directory service administrators MUST be sufficiently secured. Normal users MUST be prohibited f... |
47 | Drawing Up a Security Concept for the Use of Directory Services (S) | APP.2.1.A7 | The directory service security concept SHOULD specify rules for all the relevant topic areas. The security policies developed on this basis SHOULD be documented in writing and communicated to directory service users. |
48 | Planning of Partitioning and Replication in the Directory Service (S) | APP.2.1.A8 | The availability and protection needs of the directory service SHOULD be taken into account during partitioning. The partitioning of the directory service SHOULD be documented in writing so that it can be reconstructed manually. In order to perform replication in a timely fashion, sufficient bandwidth SHOULD be made av... |
49 | Selection of Suitable Components for Directory Services [Process Owner] (S) | APP.2.1.A9 | Suitable components SHOULD be selected for the use of a directory service. A catalogue of criteria SHOULD be drawn up and used as a basis for selecting and acquiring components for the directory service. As part of the planning and design of the directory service, requirements for its security SHOULD be formulated in a... |
50 | Active Directory | APP.2.2 | Target Object: Application / Order: R2 |
51 | Planning Active Directory [Process Owner] (B) | APP.2.2.A1 | The domain functional level selected MUST be appropriate and as high as possible. The justification for this choice SHOULD be documented appropriately. An access control policy for Active Directory MUST be developed in accordance with the requirements at hand. Administrative delegations MUST be assigned restrictive, ne... |
52 | Secure Use of DNS for Active Directory (S) | APP.2.2.A10 | Integrated DNS zones or the secure dynamic updating of DNS data SHOULD be used. Access to the configuration data of the DNS server SHOULD only be permitted from administrative accounts. The DNS cache on DNS servers SHOULD be protected against unauthorised changes. Access to the DNS service of the domain controllers SHO... |
53 | Monitoring Active Directory Infrastructure (S) | APP.2.2.A11 | Changes at the domain level and in the overall structure of Active Directory SHOULD be monitored, logged, and evaluated. |
54 | Backups for Domain Controllers (S) | APP.2.2.A12 | There SHOULD be a backup and recovery policy for domain controllers. The backup software used SHOULD be explicitly approved by the provider for use in backing up the data of domain controllers. A separate backup account with service administrator rights SHOULD be set up for the domain controllers. The number of members... |
55 | Use of Dedicated Privileged Administration Systems (H) | APP.2.2.A14 | The administration of Active Directory SHOULD be limited to dedicated administration systems. These SHOULD be subject to particularly strong hardening based on their limited tasks. |
56 | Separation of Administration and Production Environments (H) | APP.2.2.A15 | Particularly critical systems such as domain controllers and domain administration systems SHOULD be placed in a separate forest with a unilateral trust relationship towards the production forest. |
57 | Planning of Active Directory Administration [Process Owner] (B) | APP.2.2.A2 | In large domains, the administrative users MUST be divided in terms of the service and data administration pertaining to Active Directory. Here, the administrative tasks MUST also be distributed in Active Directory according to a delegation model so that there is no overlap. |
58 | Planning of Group Policy in Windows (B) | APP.2.2.A3 | There MUST be a concept for configuring group policies. Multiple overlaps MUST be avoided whenever possible in the group policy concept. It MUST be possible to recognise exceptions to the group policy concept in the documentation. All group policy objects MUST be protected by restrictive access rights. Secure specifica... |
59 | Hardening Active Directory (B) | APP.2.2.A5 | Built-in accounts MUST be configured with complex passwords. They MUST ONLY be used as emergency accounts. Privileged accounts MUST be members of the “protected users” group. Managed service accounts (for groups) MUST be used for service accounts. All domain controllers MUST be assigned restrictive access rights at the... |
60 | Maintaining the Operational Continuity of Active Directory (B) | APP.2.2.A6 | All trust relationships in AD MUST be evaluated at regular intervals. The domain administrators group MUST be empty or as small as possible. Accounts that are no longer used MUST be disabled in AD. They SHOULD be deleted after a reasonable retention period has expired. All the necessary parameters of Active Directory S... |
61 | Implementation of Secure Administration Methods for Active Directory [Process Owner] (B) | APP.2.2.A7 | It MUST be possible to clearly trace every account to an employee. The number of service administrators and data administrators for Active Directory MUST be limited to the required minimum of trustworthy persons. The default “Administrator” account SHOULD be renamed. An “Administrator” account without privileges SHOULD... |
62 | Configuration of Secure Channel in Windows (S) | APP.2.2.A8 | Secure Channel SHOULD be configured in Windows according to the security requirements and the local conditions at hand. All the relevant group policy parameters SHOULD be taken into account in the process. |
63 | Authentication Protection When Using Active Directory (S) | APP.2.2.A9 | The Kerberos authentication protocol SHOULD be used consistently in the Active Directory environment. If NTLMv2 is used temporarily for compatibility reasons, the migration to Kerberos SHOULD be planned and scheduled. LM authentication SHOULD be disabled. SMB data traffic SHOULD be signed. Anonymous access to domain co... |
64 | OpenLDAP | APP.2.3 | Target Object: Application / Order: R2 |
65 | Planning and Selecting Back Ends and Overlays for OpenLDAP (B) | APP.2.3.A1 | The use of OpenLDAP in an organisation MUST be carefully planned. If OpenLDAP is to be used together with other applications, the planning, configuration, and installation of applications and OpenLDAP MUST be coordinated. The version of the database used for data storage MUST be checked to ensure it is compatible. Back... |
66 | Secure Updating of OpenLDAP (S) | APP.2.3.A10 | When performing updates, particular attention SHOULD be paid to whether the changes relate to the back ends or overlays used, or to software dependencies. If administrators use their own scripts, they SHOULD be checked to see if they work with the updated version of OpenLDAP without any problems. The configuration and ... |
67 | Restriction of the OpenLDAP Runtime Environment (S) | APP.2.3.A11 | The slapd server SHOULD be restricted to a runtime directory. This directory SHOULD contain all configuration files and databases. |
68 | Secure Configuration of OpenLDAP (B) | APP.2.3.A3 | Secure configuration of OpenLDAP requires a correctly configured slapd server. The client applications used MUST also be securely configured. When configuring OpenLDAP, the permissions MUST be set correctly in the operating system. The default values of all relevant OpenLDAP configuration directives MUST be checked and... |
69 | Configuration of the Database Used by OpenLDAP (B) | APP.2.3.A4 | The access rights for newly created database files MUST be limited to the user ID in whose context the slapd server is being run. The standard settings of the database used by OpenLDAP MUST be adapted. |
70 | Secure Assignment of Access Rights to OpenLDAP (B) | APP.2.3.A5 | The global and database-specific access control lists maintained in OpenLDAP MUST be factored in correctly when using OpenLDAP. Database directives MUST take precedence over global directives. |
71 | Secure Authentication for OpenLDAP (B) | APP.2.3.A6 | If the directory service is to distinguish between different users, they MUST authenticate themselves appropriately. The authentication between the slapd server and communication partners MUST be encrypted. If passwords are to be stored on the clients and servers, hashed values only MUST be used. A suitable hashing alg... |
72 | Restrictions on Attributes in OpenLDAP (S) | APP.2.3.A8 | The attributes in OpenLDAP SHOULD be restricted using overlays. OpenLDAP SHOULD be modified so that values in the directory service only correspond to a specific regular expression. In addition, it SHOULD be ensured with the help of overlays that selected values only exist once in the directory tree. Such restrictions ... |
73 | Partitioning and Replication in OpenLDAP (S) | APP.2.3.A9 | OpenLDAP SHOULD be partitioned into subtrees on different servers. In such configurations, changes made to data on one server SHOULD be replicated to the other servers. The replication mode SHOULD be selected based on the network connections and availability requirements at hand. |
74 | Web Applications | APP.3.1 | Target Object: Application / Order: R2 |
75 | Use of Web Application Firewalls (H) | APP.3.1 A20 | Organisations SHOULD use web application firewalls (WAF). The configuration of a given WAF should be adapted to the web application it is meant to protect. The WAF's configuration SHOULD be checked after each web application update. |
76 | Authentication for Web Applications (B) | APP.3.1.A1 | The IT Operation Department MUST configure web applications in such a way that users have to authenticate themselves to access protected resources. An appropriate authentication method MUST be selected for this. The selection process SHOULD be documented. The IT Operation Department MUST define appropriate thresholds f... |
77 | Secure Integration of Background Systems (S) | APP.3.1.A11 | Access to background systems to which functions and data are outsourced SHOULD only be possible from defined IT systems via defined interfaces. When communicating across network and site boundaries, data traffic SHOULD be authenticated and encrypted. |
78 | Secure Configuration of Web Applications (S) | APP.3.1.A12 | A web application SHOULD be configured in such a way that its resources and functions can only be accessed using the secured communication paths specified for this purpose. Access to resources and functions that are not required SHOULD be disabled. If this is not possible, such access SHOULD be restricted as far as pos... |
79 | Protection of Confidential Data (B) | APP.3.1.A14 | The IT Operation Department MUST ensure that access data for the web application is protected from unauthorized access on the server side using secure cryptographic algorithms. Salted hash methods MUST be used for this purpose. The files containing the source code of the web application MUST be protected against unauth... |
80 | Secure HTTP Configuration of Web Applications (S) | APP.3.1.A21 | To protect against clickjacking, cross-site scripting, and other attacks, the IT Operation Department SHOULD set appropriate HTTP response headers. At minimum, the following HTTP headers SHOULD be used: Content-Security-Policy, Strict-Transport-Security, Content-Type, X-Content-Type-Options, and Cache-Control. The HTTP... |
81 | Penetration Testing and Auditing (S) | APP.3.1.A22 | Web applications SHOULD be checked for security issues at regular intervals. In particular, audits SHOULD be performed regularly. The results SHOULD be documented transparently, protected adequately, and handled confidentially. Deviations SHOULD be investigated. The results SHOULD be presented to the CISO. |
82 | Controlled Integration of Files and Content in Web Applications (B) | APP.3.1.A4 | If a web application offers an upload function for files, this function MUST be restricted as far as possible by the IT Operation Department. In particular, the allowed file size, allowed file types, and allowed storage locations MUST be defined. The users allowed to use the upload function MUST be defined. Access and ... |
83 | Protection Against Unauthorised Automated Use of Web Applications (B) | APP.3.1.A7 | The IT Operation Department MUST ensure that the web application is protected against unauthorised automated use. However, these efforts MUST take into account the impact that the protection mechanisms will have on the ability of authorised users to use the application. If the web application contains RSS feeds or othe... |
84 | System Architecture of a Web Application [Procurement Department] (S) | APP.3.1.A8 | Security aspects SHOULD be considered early on in the planning stage. It SHOULD also be ensured that the architecture of the web application maps the exact business logic of the organisation and implements it correctly. |
85 | Web Application Procurement (S) | APP.3.1.A9 | In addition to the general aspects of software procurement, the organisation SHOULD, at minimum, consider the following when procuring web applications: • Secure input validation and output encoding in the web application • Secure session management • Secure cryptographic procedures • Secure authentication procedures •... |
86 | Web Servers | APP.3.2 | Target Object: Application / Order: R2 |
87 | Secure Web Server Configuration (B) | APP.3.2.A1 | After the IT Operation Department has installed a web server, it MUST perform a secure basic configuration. To that end, it MUST specifically assign the web server process to a user account with minimal rights. The web server MUST also be executed in an encapsulated environment whenever this is supported by the operati... |
88 | Selecting an Appropriate Web Host (S) | APP.3.2.A10 | If an organisation opts to use an external webhosting provider instead of operating its web server itself, the organisation SHOULD pay attention to the following points when selecting a suitable provider: • The manner in which the services are to be rendered SHOULD be contractually agreed. Security aspects SHOULD be in... |
89 | Encryption via TLS (B) | APP.3.2.A11 | The web server MUST provide secure encryption via TLS (HTTPS) for all connections that pass through untrusted networks. If it is necessary to use obsolete procedures for compatibility reasons, these SHOULD be limited to as few cases as possible. If an HTTPS connection is used, all content MUST be delivered via HTTPS. M... |
90 | Suitable Handling of Errors and Error Messages (S) | APP.3.2.A12 | HTTP information and displayed error messages SHOULD NOT show the product name or the version of the web server used. Error messages SHOULD not reveal details regarding system information or configurations. The IT Operation Department SHOULD ensure that the web server only outputs general error messages that inform the... |
91 | Access Control for Web Crawlers (S) | APP.3.2.A13 | Web crawler access SHOULD be regulated in accordance with the robots exclusion standard. Content SHOULD be provided with access protection to safeguard it against web crawlers that do not comply with this standard. |
92 | Integrity Checks and Protection Against Malware (S) | APP.3.2.A14 | The IT Operation Department SHOULD regularly check the integrity of the configurations of the web server and the files it provides and ensure they have not been modified by attackers. The files intended for publication SHOULD be regularly checked for malware. |
93 | Redundancy (H) | APP.3.2.A15 | Web servers SHOULD be designed to be redundant. The Internet connection of a web server and other IT systems (such as the web application server) SHOULD also be designed with redundancy. |
94 | Penetration Testing and Auditing (S) | APP.3.2.A16 | Web servers SHOULD be checked for security issues at regular intervals. Audits SHOULD also be performed regularly. The results SHOULD be documented transparently, protected adequately, and handled confidentially. Deviations SHOULD be investigated. The results SHOULD be presented to the CISO. |
95 | Protection Against Denial-of-Service Attacks (H) | APP.3.2.A18 | A web server SHOULD be monitored continuously. Furthermore, safeguards that prevent or at least mitigate DDoS attacks SHOULD be defined and implemented. |
96 | Protection of Web Server Files (B) | APP.3.2.A2 | The IT Operation Department MUST protect all files on the web server (including scripts and configuration files in particular) so that they cannot be read or changed without authorisation. It MUST be ensured that web applications can only access a defined directory tree (the WWW root directory). The web server MUST be ... |
97 | Appointing Contact Persons [Central Administration] (S) | APP.3.2.A20 | An organisation that maintains extensive websites SHOULD designate a contact person for them. Processes, procedures, and persons responsible for problems or security incidents SHOULD be specified. The organisation SHOULD post a contact option on its website that enables external parties to report security issues to the... |
98 | Protecting File Uploads and Downloads (B) | APP.3.2.A3 | All files published using the web server MUST be checked in advance for malware. A maximum size for file uploads MUST be specified. Sufficient storage space MUST be reserved for uploads. |
99 | Logging of Events (B) | APP.3.2.A4 | The web server MUST log at least the following events: • Successful attempts to access resources • Failed attempts to access resources due to a lack of authorisations, unavailable resources, or server errors • General error messages The log data SHOULD be analysed regularly. |
100 | Authentication (B) | APP.3.2.A5 | When clients authenticate themselves to a web server using passwords, these passwords MUST be stored in a way that is cryptographically secured and protected from unauthorised access. |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 5