Wallet Best Practice - Revision history

Tom: /* Solutions */

2024-10-27T00:43:37Z

‎Solutions

Tom: /* References */

2024-10-27T00:38:24Z

‎References

Tom: /* Full Title or Meme */

2024-10-27T00:37:01Z

‎Full Title or Meme

Tom: /* References */

2024-02-28T05:27:41Z

‎References

Tom at 05:26, 28 February 2024

2024-02-28T05:26:34Z

Tom: /* Full Title or Meme */

2023-10-08T05:32:24Z

‎Full Title or Meme

Tom: /* Full Title or Meme */

2023-10-07T17:42:04Z

‎Full Title or Meme

Tom: Created page with "==Full Title or Meme== This is a design that will meet the requirements of North American governments. * [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-cert..."

2023-10-07T05:56:48Z

Created page with "==Full Title or Meme== This is a design that will meet the requirements of North American governments. * [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-cert..."

New page

==Full Title or Meme==

This is a design that will meet the requirements of North American governments.

* [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-certified/ AWS-LC is now FIPS 140-3 certified]
* Google open source to OWF

@@ Line 13: / Line 13: @@
 * https://github.com/google/identity-credential
 ==Solutions==
-* 2024-08-06 [https://github.com/openwallet-foundation/safe-wallet-sig/blob/main/docs/wallet-safety-guide.md OWF Wallet Safety Guide]] Mostly a collection of high level principles that are not actionable.
+* 2024-08-06 [https://github.com/openwallet-foundation/safe-wallet-sig/blob/main/docs/wallet-safety-guide.md OWF Wallet Safety Guide]  Mostly a collection of high level principles that are not actionable.
 ==References==
 [[Category: Best Practice]]

@@ Line 17: / Line 17: @@
 [[Category: Best Practice]]
 * See wiki page on [[Cybersecurity Framework for Mobile Credentials]].
 [[Category: Best Practice‏‎]]
 [[Category: Mobile]]

@@ Line 1: / Line 1: @@
 ==Full Title or Meme==
+Rules for building wallets that will be safe.
 This is a design that will meet the requirements of North American governments.
@@ Line 11: / Line 12: @@
 * Google open source to OWF
 * https://github.com/google/identity-credential
 ==References==

← Older revision		Revision as of 05:27, 28 February 2024
Line 15:		Line 15:
	* See wiki page on [[Cybersecurity Framework for Mobile Credentials]].		* See wiki page on [[Cybersecurity Framework for Mobile Credentials]].

		+	[[Category: Best Practice‏‎]]
	[[Category: Mobile]]		[[Category: Mobile]]

← Older revision		Revision as of 05:26, 28 February 2024
Line 11:		Line 11:
	* Google open source to OWF		* Google open source to OWF
	* https://github.com/google/identity-credential		* https://github.com/google/identity-credential
		+
		+	==References==
		+	* See wiki page on [[Cybersecurity Framework for Mobile Credentials]].
		+
		+	[[Category: Mobile]]

@@ Line 4: / Line 4: @@
 * [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-certified/ AWS-LC is now FIPS 140-3 certified]
-* Google open source to OWF
 AWS-LC FIPS 140-3 certificate: AWS-LC is an open source cryptographic library that is a fork from Google’s BoringSSL.1 It has been validated by NIST as a FIPS 140-3, level 1, cryptographic module, which is the latest and most stringent version of the standard for cryptographic modules for the U.S. and Canadian Federal governments.
 Performance and security benefits: AWS-LC is tailored by the AWS Cryptography team to meet the needs of AWS services, which require fast and verified cryptography. It includes low-level implementations that target 64-bit Arm and x86 processors, which improve the performance of AWS services such as Amazon S3. It also integrates CPU-Jitter as the source of entropy, which ensures the security strength of the keys it generates.2
 Future integrations and versions: AWS-LC provides an API for direct integration with C and C++ applications. It will also be integrated with aws-lc-rs and ACCP 2.0 libraries, which are compatible with Rust and Java applications respectively. AWS is committed to maintaining and validating new versions of the AWS-LC FIPS module as it grows.3

← Older revision		Revision as of 17:42, 7 October 2023
Line 5:		Line 5:
	* [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-certified/ AWS-LC is now FIPS 140-3 certified]		* [https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-certified/ AWS-LC is now FIPS 140-3 certified]
	* Google open source to OWF		* Google open source to OWF
		+	AWS-LC FIPS 140-3 certificate: AWS-LC is an open source cryptographic library that is a fork from Google’s BoringSSL.1 It has been validated by NIST as a FIPS 140-3, level 1, cryptographic module, which is the latest and most stringent version of the standard for cryptographic modules for the U.S. and Canadian Federal governments.
		+	Performance and security benefits: AWS-LC is tailored by the AWS Cryptography team to meet the needs of AWS services, which require fast and verified cryptography. It includes low-level implementations that target 64-bit Arm and x86 processors, which improve the performance of AWS services such as Amazon S3. It also integrates CPU-Jitter as the source of entropy, which ensures the security strength of the keys it generates.2
		+	Future integrations and versions: AWS-LC provides an API for direct integration with C and C++ applications. It will also be integrated with aws-lc-rs and ACCP 2.0 libraries, which are compatible with Rust and Java applications respectively. AWS is committed to maintaining and validating new versions of the AWS-LC FIPS module as it grows.3