Posts

Showing posts with the label Security Activity

XML Signature Syntax and Processing Version 2.0 Note Published

23 July 2015 The  XML Security Working Group  has published a Group Note of  XML Signature Syntax and Processing Version 2.0 . This informative W3C Working Group Note describes XML digital signature processing rules and syntax. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. Learn more about the  Security Activity . Introduction: Mastering Digital Growth in 2025—From SEO to Social Media and AI In 2025, digital success isn’t just about having an online presence—it’s about strategically connecting the dots between SEO, web design, content creation, and social media. For small businesses and marketers alike, staying ahead means embracing the latest tools and trends that shape how we rank, engage, and grow online. Whether you're aiming to  win local search  with cutting-edge  SEO for Small Business in 2025: H...

W3C Invites Implementations of Content Security Policy Level 2

19 February 2015 The Web Application Security Working Group has published a Candidate Recommendation of Content Security Policy Level 2 . This specification updates Content Security Policy, fine-tuning the existing policy options, and introducing a number of new mechanisms that site authors can use to mitigate the risk of content injection and related attacks. Major differences from Content Security Policy Level 1 may be found in Section 1.1 of the document . With this publication, we move the earlier edition off the Recommendation Track to a Note ( Content Security Policy 1.0 ) and invite implementers to share their experience with CSP Level 2. Learn more about the Security Activity .

WebCrypto Key Discovery Working Draft Published

22 August 2013 The Web Cryptography Working Group has published a Working Draft of WebCrypto Key Discovery . This specification describes a JavaScript API for discovering named, origin-specific pre-provisioned cryptographic keys for use with the Web Cryptography API. Pre-provisioned keys are keys which have been made available to the user agent by means other than the generation, derivation, importation functions of the Web Cryptography API. Origin-specific keys are keys that are available only to a specified origin. Named keys are identified by a name assumed to be known to the origin in question and provisioned with the key itself. Learn more about the Security Activity .

Web Cryptography API Draft Published

25 June 2013 The Web Cryptography Working Group has published a Working Draft of Web Cryptography API . This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. Learn more about the Security Activity .

Three drafts published by the Web Cryptography Working Group

08 January 2013 The Web Cryptography Working Group has published three documents . A Working Draft of Web Cryptography API . This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. A First Public Working Draft of WebCrypto Key Discovery . This specification describes a JavaScript API for discovering named, origin-specific pre-provisioned cryptographic keys for use with the Web Cryptography API. Pre-provisioned keys are keys which have been made available to the UA by means other than the generation, derivation, imporation functions of the Web Cryptog...

User Interface Safety Directives for Content Security Policy Draft Published

The Web Application Security Working Group has published the First Public Working Draft of User Interface Safety Directives for Content Security Policy . This document defines directives for the Content Security Policy mechanism to declare a set of input protections for a web resource's user interface, defines a non-normative set of heuristics for Web user agents to implement these input protections, and a reporting mechanism for when they are triggered. Learn more about the Security Activity .

Web Cryptography API Draft Published

13 September 2012 The Web Cryptography Working Group has published the First Public Working Draft of Web Cryptography API . This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Key storage is provided for both temporary and permanent keys. Access to keying material is contingent on the same origin policy. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications. Learn more about the Security Activity .

Content Security Policy Draft Published

The Web Application Security Working Group has published the First Public Working Draft of Content Security Policy . This document defines Content Security Policy, a mechanism web applications can use to mitigate the broad class of content injection vulnerabilities, such as cross-site scripting (XSS). Content Security Policy is a declarative policy that lets the authors (or server administrators) of a web application restrict from where the application can load resources. Learn more about the Security Activity .