## 5 M2M Security
\begin{table}
\begin{tabular}{c l l l l} \hline \hline  & **Technology, What to Solve?** & \multicolumn{2}{c}{**Forum(s), References**} & \multicolumn{1}{c}{**Main Contribution**} \\ \hline - & JSON security & - & IETF’s JavaScript Object Signing and & Standardizing integrity protection and \\ - & To provide authentication, & Encryption (JOSE) working group & encryption security services, in order to \\  & integrity and confidentiality, & - & Used, e.g., in/by SAML 2.0, WS-Federation, & increase interoperability of security features \\  & access control and resource & OpenID, OAuth 2.0, XMPP, ALTO and to & between protocols that use JSON. \\  & control & & provide integrity of exist (alarms) & \\ \hline - & XML security & W3C’s XML security working group & XML Signature provides integrity, message \\ - & To provide authentication, & & authentication, and/or signer authentication \\  & integrity and confidentiality. & & services for data. XML Encryption specifies \\  & & & a process for encrypting data and \\  & & & representing the result in XML. XKMS \\  & & & specifies protocols for distributing and \\  & & & registering public keys. \\ \hline HTTP Strict Transport & IETF’s Web Security (websec) & HSTS is designed to allow web sites or http \\ Security (HSTS) & working group & servers to tell users’ browsers or http clients \\  & & & that they want to communicate only over an encrypted connection. \\ \hline - & DNSSEC & IETF’s Domain Name System Security & Enhancements to the secure DNS protocol. \\ - & To provide secure DNS. & (dnssec) working group & \\ \hline ETSI M2M security architecture & ETSI & - & Pre-provisioned device/gateway \\  & & & credential types, e.g., SIM/AKA or \\  & & & X.509v3 certificates. \\  & & & - & Defining M2M bootstrap procedures \\  & & & based on GBA, TLS or EAP/PANA. \\  & & & - & Securing M2M service connection by \\  & & & GBA, TLS or EAP/PANA. \\  & & & - & Securing mld by TLS or DTLS, XML \\  & & & security or relying access \\  & & & network security. \\ \hline - & SASL & IETF’s Simple Authentication and Security & A framework for authentication and data \\ - & To provide authentication. & Layer (SASL) concluded working group & security in Internet protocols. Application \\  & & & protocol that uses SASL can in theory use \\  & & & any authentication mechanisms supported \\  & & & by SASL. \\ \hline - & HTTPS & IETF & Usage of TLS to secure HTTP connections \\ - & Authentication of end-points, & & & \\  & protection against MitM attacks, & & & \\  & encryption of communication & & \\ \hline - & AAA protocols & - & IETF’s Authentication, Authorization and & - & Diameter \\ - & To authenticate entity’s & Accounting (AAA) concluded working & - & Radius \\ - & identification & group, RADIUS Extensions (radext) & - & 3 GPP EPS AAA \\ - & To authorize the entity & & working group, Diameter maintenance and & \\ - & To account aka track a network & & Extensions (dime) working group & \\  & resource consumption & - & 3 GPP & \\ \hline - & Trusted Key Distribution & - & MIT (Kerberos) & - & Kerberos 5 \\  & Centers (KDC) & - & OpenID Foundation & - & OpenID \\ - & Authentication and key & & & - & Single Sign-On (SSO) \\  & exchange, sometimes also access & & & \\  & control & & & \\ \hline \hline \end{tabular}
\end{table} 
Table 7: Security technologies applicable for applications layer.