Attestation
Depending on the security requirements for your application, you may need to use attestation to do business.
Attestation is a method for software to prove its identity during normal operations. The goal of attestation is to prove to a remote party that your operating system and application software are intact and trustworthy.
The best method of implementing attestation is through Security policies, specifically using the policy type drop-down and selecting Multi-factor authentication or User consent.
For more information, see:
- Enforcing policies from the Security Policies landing page.
- Security policies.
- Security policies settings.
- Using the login policies settings.
Attestations at Pega
Pega keeps pace with emerging and established international and local standards and regulations, maintaining extensive compliance certifications, attestations, and accessibility, plus third-party assessments.
Pega Platform supports the following types of attestation:
- California Consumer Privacy Act (CCPA).
- United States Food and Drug administration (FDA).
- General Data Protection Regulation (GDPR).
- Health Insurance Portability and Accountability Act (HIPAA).
- Health Information Technology for Economic and Clinical Health (HITECH).
- Privacy Shield Framework.
For more general information about these policies, see their official websites.
For more information on how these are used in Pega Platform, see:
Previous topic Verifying a one-time password by calling an API Next topic Configuring a token credentials authentication service