Click on the interactive map below or utilise the filtering interface on the side to browse the items that are currently in our Standards Watch*.
The Standards Watch of StandICT.eu monitors the status of ICT standards at international level, starting from the five priority areas of the Digital Single Market: 5G communications,cloud computing,cybersecurity,data technology, and IoT – Internet of Things.
In particular, special attention is given to the rapidly evolving ICT topics of: Artificial Intelligence, Big Data, IoT.
Gradually, the Standards Watch will be expanded to other ICT domains and topics, with the aim of better identifying gaps, needs & opportunities and consequently stimulating European Experts to pursue the openings granted by the StandICT.eu initiative.
The present document specifies high-level provisions for the security of consumer devices that are connected to network infrastructure, such as the Internet or home network, and their associated services. A non-exhaustive list of examples include:
The present document defines security solutions applicable within the M2M system.
This document describes how an author can set a referrer policy for documents they create, and the impact of such a policy on the Referer HTTP header for outgoing requests and navigations.
The Permissions Standard defines common infrastructure for other specifications that need to interact with browser permissions. It also defines an API to allow web applications to query and request changes to the status of a given permission.
This document defines an imperative mechanism which allows web developers to instruct a user agent to clear a site’s locally stored data related to a host.
This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.
This specification describes an imperative API enabling a website to request a user’s credentials from a user agent, and to help the user agent correctly store user credentials for future use.
This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent.
This specification defines a mechanism that allows developers to selectively enable and disable use of various browser features and APIs.