Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
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.
Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
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.
In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.
In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.
When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
.svg)
.svg)
.svg)
Break down the framework into specific obligations that must be met.
.svg)
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.
