Lines Matching full:should

250       - Disclosed vulnerabilities should be acted on in a timely manner.
257       - Manufacturers should continually monitor for, identify and rectify security
266       - All software components in consumer IoT devices should be securely updatable.
288       - Automatic mechanisms should be used for software updates.
295       - The device should check after initialization, and then periodically, whether
304         should be enabled in the initialized state and configurable so that the user
327       - The device should verify the authenticity and integrity of software updates.
343       - The manufacturer should inform the user in a recognizable and apparent manner
352       - The device should notify the user when the application of a software update
370         support and a defined support period should be published by the manufacturer in an
379         should be isolable and the hardware replaceable.
434       - The consumer IoT device should use reviewed or evaluated implementations to deliver
442       - Cryptographic algorithms and primitives should be updatable.
449       - Access to device functionality via a network interface in the initialized state should
467       - Critical security parameters should be encrypted in transit, with such encryption
506       - Device hardware should not unnecessarily expose physical interfaces to attack.
520       - The manufacturer should only enable software services that are used or required for
528       - Code should be minimized to the functionality necessary for the service/device to operate.
535       - Software should run with least necessary privileges, taking account of both security
543       - The device should include a hardware-level access control mechanism for memory.
550       - The manufacturer should follow secure development processes for software deployed on
558       - The consumer IoT device should verify its software using secure boot mechanisms.
566       - If an unauthorized change is detected to the software, the device should alert the
567         user and/or administrator to the issue and should not connect to wider networks than
576         especially associated services, should be protected, with best practice cryptography.
600       - Resilience should be built in to consumer IoT devices and services, taking into
608       - Consumer IoT devices should remain operating and locally functional in the case of a
609         loss of network access and should recover cleanly in the case of restoration of a
617       - The consumer IoT device should connect to networks in an expected, operational and
627         and measurement data, it should be examined for security anomalies.
642       - The consumer should be provided with functionality on the device such that personal
650       - Users should be given clear instructions on how to delete their personal data.
657       - Users should be provided with clear confirmation that personal data has been deleted
665       - Installation and maintenance of consumer IoT should involve minimal decisions by the
666         user and should follow security best practice on usability.
673       - The manufacturer should provide users with guidance on how to securely set up their device.
680       - The manufacturer should provide users with guidance on how to check whether their
724         processing of personal data should be kept to the minimum necessary for the