+APP.3.3 File Servers
---+APP.3.3.G1. File Server Failure
---+APP.3.3.G2. Insufficient File Server Characteristics
---+APP.3.3.G3. Insufficient Checking of Stored Files
---+APP.3.3.G4. Insufficient Access Authorisation Concept
---+APP.3.3.G5. Unstructured Data Storage
---+APP.3.3.G6. Loss of Data Stored on File Servers
---+APP.3.3.G7. Ransomware
---+APP.3.3.A2 Use of RAID Systems (B)
---+APP.3.3.A3 Use of Anti-Virus Programs (B)
---+APP.3.3.A15 Planning File Servers (B)
---+APP.3.3.A6 Acquiring a File Server and Selecting a Service (S)
---+APP.3.3.A7 Selecting a File System (S)
---+APP.3.3.A8 Structured Data Storage [User] (S)
---+APP.3.3.A9 Secure Storage Management (S)
---+APP.3.3.A11 Using Storage Restrictions (S)
---+APP.3.3.A14 Using Error Correction Codes (S)
---+APP.3.3.A12 Data Encryption (H)
---+APP.3.3.A13 Replicating Between Locations (H)
|
APP.3.3 File Servers
IntroductionA file server is a network server that provides files centrally from internal or networked hard drives for all users or clients with corresponding access authorisation. Authorised users can thus share data without having to transport it to removable media or distribute it by e-mail, for example. Because the data is stored centrally, it can be structured and provided in various directories and files. With file servers, access rights to files can also be assigned centrally. Furthermore, storing all data in a central location simplifies the creation of backups. A file server mainly manages mass-storage devices connected via interfaces such as SCSI (Small Computer System Interface) or SAS (Serial Attached SCSI). The storage memory itself is either located directly within the server's casing or connected externally. The latter is often referred to as ‘directly attached storage’ (DAS). A file server can be operated on conventional server hardware or a dedicated appliance. For large data volumes, central storage area network (SAN) devices can also be connected via host bus adapters (HBA) in the server, as well as to SAN switches. ObjectiveThis module describes the main threats specific to file servers and the resulting requirements for the secure operation of such servers. Scoping and ModellingModule APP.3.3 File Servers must be applied once to each file server in the information domain in question. This module includes basic specifications which must be observed and met when operating file servers. The general and operating-system-specific aspects of a server are not included in this module. These aspects are addressed in module SYS1.1 General Server and in the relevant operating-system-specific modules of the IT Systems layer, e.g. SYS.1.3 Linux and Unix Servers or SYS.1.2.2 Windows Server 2012. Requirements for network-based storage systems or storage networks are not described. These are discussed in module SYS.1.8 Storage Solutions. Dedicated services for operating a file server (e.g. Samba) are also not addressed. The Samba service is covered in module APP.3.4 Samba. When securing a file server, it is important to assign rights to files in a restrictive manner. Further requirements in this regard can be found in module ORP.4 Identity and Access Management. Furthermore, this module does not cover methods of securing the information stored on a file server. On this topic, the requirements of module CON.3 Backup Concept must be met. Useful ResourcesNo further information is available for module APP.3.3 File Servers.
1. Oversigt
| Titel |
Standard |
|
APP.3.3.A2 Use of RAID Systems (B)
|
The IT Operation Department MUST define whether a RAID system should be used on a file server. Any decision against such a system MUST be documented in a transparent manner. If a RAID system is to be used, the IT Operation Department MUST decide: - what RAID level should be used
- what length of time will be allowed for a RAID rebuild process
- whether to use a software or a hardware RAID
Hot spare hard disks SHOULD be available in a RAID.
|
|
APP.3.3.A3 Use of Anti-Virus Programs (B)
|
All data MUST be scanned for malware by a virus protection programme before being stored on the file server.
|
|
APP.3.3.A15 Planning File Servers (B)
|
Before an organisation introduces one or more file servers, it SHOULD decide what the file servers will be used for and what information will be processed on them. The organisation SHOULD plan each file server function to be used, including its security aspects. Personal computers MUST NOT be used as file servers. File server storage space MUST be adequately sized. Sufficient storage reserves SHOULD also be kept available. Only mass storage designed for continuous operation SHOULD be used. The speed and connections of mass storage MUST be appropriate for its intended use.
|
|
APP.3.3.A6 Acquiring a File Server and Selecting a Service (S)
|
Appropriate file server software SHOULD be selected. The file server service SHOULD support the intended use of the file server—for example, the integration of network drives on clients, streaming of multimedia content, the transfer of boot images from diskless IT systems, or simple file transfers via FTP. Performance, storage capacity, bandwidth, and the number of people who will be using it SHOULD be considered when purchasing a file server.
|
|
APP.3.3.A7 Selecting a File System (S)
|
The IT Operation Department SHOULD create a requirements list and use it as a basis for evaluating the file systems of different file servers. The file system selected SHOULD meet the organisation’s standards. The file system SHOULD also provide a journaling function. Moreover, it SHOULD have a mechanism that prevents several users or applications from accessing a file with write permissions at the same time.
|
|
APP.3.3.A8 Structured Data Storage [User] (S)
|
A structure for storing data SHOULD be specified. Users SHOULD be informed regularly of the requirements of structured data storage. Files SHOULD only be stored on a file server in a structured manner. The types of data that can be stored locally those that can be kept on a file server SHOULD be specified in writing. Program and work files SHOULD be stored in separate directories. The organisation SHOULD regularly check compliance with the requirements for structured data storage.
|
|
APP.3.3.A9 Secure Storage Management (S)
|
The IT Operation Department SHOULD regularly check whether the mass storage of file servers is still working as intended. Suitable backup storage SHOULD be kept available. If a storage hierarchy (primary, secondary and tertiary storage) has been established, (partially) automated storage management SHOULD be used. If data is distributed automatically, the proper functioning of the distribution method used SHOULD be checked manually at regular intervals. At minimum, unauthorised attempts to access files and changes in access rights SHOULD be logged.
|
|
APP.3.3.A11 Using Storage Restrictions (S)
|
The IT Operation Department SHOULD consider setting limits (quotas) on storage space for individual users if there are multiple users on a file server. As an alternative, mechanisms of the file or operating system in question SHOULD be used that warn users or only grant write privileges to the system administrator if the hard drive capacity reaches a specific level.
|
|
APP.3.3.A14 Using Error Correction Codes (S)
|
The IT Operation Department SHOULD use an error-detecting or error-correcting file system. Sufficient storage space SHOULD be provided for this purpose. The IT Operation Department SHOULD take into account that, depending on the method used, errors can only be detected with a certain probability and can only be removed to a limited extent.
|
|
APP.3.3.A12 Data Encryption (H)
|
The mass storage devices of a file server SHOULD be encrypted at the file system or hardware level. If hardware encryption is used, products with a certified encryption function SHOULD be used. It SHOULD be ensured that the virus protection program in use can scan encrypted data for malware.
|
|
APP.3.3.A13 Replicating Between Locations (H)
|
For high-availability file servers, data SHOULD be replicated appropriately across several mass storage devices. Data SHOULD also be replicated between independent file servers located at independent sites. To this end, a suitable replication mechanism SHOULD be selected by the IT Operation Department. Sufficiently accurate time services SHOULD be used and operated so that the replication can work as intended.
|
1.1 Referencer
1.2 Identificerede krav
1.3 Relaterede reguleringer
2. Identificerede krav
3. Relaterede reguleringer
Reguleringer
| Kilde |
Regulering |
Linkede sager
|