Skip to main content

Attestation

Suggest edit
Updated on July 1, 2021

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.

The Policy type selector options: Multi-factor authenticaiton or user consent
An image of the UI which displays the Policy type drop down options: Multi-factor authenticaiton or user consent

For more information, see:

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
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us