6.5. Testing Your Cloud Security for Salesforce Installation

Before you test your installation, be sure to create a test user.

Successful Login

Setup

Note: Make sure your Salesforce setup is correct and your device is compliant.

Test your installation in all three modes: Enforce, Monitor, Disable. In each case, the outcome must be the same.

Action

Login with your test user.

Expected Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then the user is logged in to Salesforce.

Admin User

Under the OPSWAT MetaAccess Logs tab, a log record has been created with hardware ID and device status compliant.

Non-Compliant Device

Setup

Note: Make sure your Salesforce setup is correct, but your test device is non-compliant.

Action

Login with your test user.

Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then login is interrupted and the Error page appears, displaying that your device is non-compliant.

Admin User

Under the OPSWAT MetaAccess Logs tab, a log record has been created with the hardware id and device status as non_compliant.

Non-Compliant Device (Monitor Mode, Log Only)

Setup

Before you test, make sure your Policy Setting Mode is set to Monitor.

Note: Make sure your Salesforce setup is correct, but your test device is non-compliant.

Action

Login with your test user.

Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then the user is logged in to Salesforce.

Admin User

Under the OPSWAT MetaAccess Logs tab, a log record has been created with the hardware id and device status as non_compliant.

Non-Compliant Device (Disable Mode)

Setup

Before you test, make sure your Policy Setting Mode is set to Disable.

Note: Make sure your Salesforce setup is correct, but your test device is non-compliant.

Action

Login with your test user.

Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then the user is logged in to Salesforce.

Admin User

Under the OPSWAT MetaAccess Logs tab, NO log has been created.

No Connection to MetaAccess Server

Setup

Make an incorrect entry into your Salesforce configuration (for example: wrong client key).

You can test with both a compliant and non-compliant device. In each case, the outcome must be the same.

Action

Login with your test user.

Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then the error page shows that the connection has failed. There is an option to Contact Admin. By clicking Contact Admin, the System Administrator that was set up in the configuration receives an email of the error.

Admin User

Under the OPSWAT MetaAccess Logs tab, a log has been created with the hardware id, but no device status.

5/b If configuration is set to Monitor mode, login occurs and log is created.

5/c If configuration is set to Disable mode, login occurs and no log is created.

MetaAccess is not Installed on your Device

Setup

You can test with both a compliant and non-compliant device. In each case, the outcome must be the same.

Make sure MetaAccess is not installed on your test device.

Action

Login with your test user.

Outcome

After authentication, the OPSWAT MetaAccess Verification page appears for a second, then the error page shows that MetaAccess is not installed on your test. There is an option to download it by clicking a button. It should redirect you to the MetaAccess download page.

Admin User

Under the OPSWAT MetaAccess Logs tab, a log has been created with no hardware id and no device status.

6/b If configuration is set to Monitor mode, login occurs and a log is created.

6/c If configuration is set to Disable mode, login occurs and no log is created.