Security Settings

Security Settings

Account Settings

These Account Settings security options apply only to users in the account who do not have permission to view full credit card numbers. (PCI Compliance standards require users that have permission to view full credit card numbers to have a session timeout of 15 minutes, and password expiration of 90 days.)

Note: A user's password expires after that number of days, regardless of when they last logged in.

Security Settings

If either Full CC Number Access option is selected at the account level ( Account Settings > Implementation > Products ), and the user has both of those options off at the event level ( Plan > Configure > Options ), then that user’s security settings are determined by these Account Settings.

If either Full CC Number Access option is selected at the account level ( Account Settings > Implementation > Products ), and the user has either of those option on at the event level ( Plan > Configure > Options ), then that user's security settings are determined by PCI Compliance standards. The value of these options at the event level does not affect the user’s security settings ( Account Settings > Administration > Users ).

Best Practices

The session timeout and password expiration options required by PCI Compliance are very restrictive and will be cumbersome to most users.

Therefore, unless access to the Full CC Numbers is absolutely required, the account Administrator should turn off the Financial and/or Accommodation modules so these Account Setting options can be utilized.

Other Settings

NOTE: When you send email to registrants, the From and To fields saved on the email template take precedence over the choice on this Security Settings page (and over the Event Contact information in the event.) CAUTION: If you select the second option, Use Event Registration Contact, emails sent from your domain through Certain may be rejected or marked as spam by recipient mail servers that enforce DMARC. To pass DMARC checks for email sent from your domain through Certain, you will need to set up Sender Authentication. This involves adding three (3) DNS records to your FROM domain so that messages Certain sends on your behalf are properly aligned for SPF, DKIM, and DMARC. How to set up Sender Authentication:

1. Email help@certain.com and let us know the FROM address domain (or domains) you plan to use.

2. Our Support team will generate the three DNS records specific to your domain and send them back to you.

3. Add the provided records to your domain's DNS configuration.

4. Once the records have propagated, email sent from Certain using a FROM address on that domain will pass DMARC at the recipient.

For more information on DMARC, SPF, and DKIM, see dmarc.org and openspf.org.

Caution: If this check box is cleared, then be sure to always have custom registration statuses set up in every event, since the status is a required field on registrations.

Source:

Keywords: Security Settings, PCI Compliance, DMARC