Identify devices in use at the organisation in accordance with the process described in 1.2.1. a) Identify information such as network addresses, hardware addresses, device names, department affiliation and whether the devices are managed by the organisation. Every device with an IP address on the network should be included on the list, including stationary and portable computers, servers, network equipment (routers, switches, firewalls etc.), printers, storage networks, IP phones, IoT devices etc. b) Create a list of all mobile devices and storage media in use outside the organisation’s network which contain organisation data. c) Create a plan for managing devices not approved for use at the organisation (see 1.2.2). For access control, see 2.4.1.b. d) The organisation should also maintain a list of virtual devices (whether they are running at the organisation’s premises or in a provider’s cloud). Such devices are often temporary (e.g. stateless virtual desktops), so one can simplify this by keeping in the inventory only the templates that the virtual devices are based on. Keeping a list of virtual devices running in a provider's cloud is strictly only necessary when buying IaaS. The process described above can be simplified by being consistent in allowlisting all devices (and/or wired and wireless network connections) on the organisation’s network. See also principle 2.4 – Protect the organisations networks.
Organisation must maintain a listing of used data systems and their owners. Owner is responsible for completing the related documentation and possible other security actions directly related to the data system.
Data system documentation must include at least:
The organization shall list all relevant protected assets to determine ownership and to ensure that security measures cover all necessary items.
A large portion of the protected assets (including data sets, data systems, personnel / units, and partners) are treated through other tasks. In addition, the organization must list other important assets, which may be, depending on the nature of its operations, e.g. hardware (servers, network equipment, workstations, printers) or infrastructure (real estate, power generation, air conditioning). In addition the organization should make sure that relevant external devices are documented.
The security policies defined in the mobile device management system aim to protect the organization’s data. For example, to reduce the risk of losing devices, you can specify that the device be locked after 5 minutes of inactivity or that the device be completely wiped after 3 failed login attempts.
It may make sense to test new policies first with a small group of users. Policies also require oversight. You can initially select a setting for policies that informs the administrator of settings that violate the policy, but does not completely block access.
The devices must be registered in the mobile device management system in order to obtain a unique identifier for the device and to use the management features. When purchasing new devices, the devices are always registered in the mobile device management system.
In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.
.png)
Elevate Your Knowledge with Exclusive Access to Weekly Webinars, Video Courses, Help Articles, and Blogs.
