Within the Security Configurations tab in Q2 Console Reporting, FIs can monitor, edit, and improve their currently implemented Q2 Patrol configurations.
Q2 Patrol is a Q2 security offering that detects potentially fraudulent online banking sessions based on historical knowledge about an end user's typical behaviors. Q2 Patrol uses two scoring models—the Login model and the Endpoint Interrogation model—to flag if an end user's login is suspect.
If the end user's session has been deemed suspect, the end user will need to provide either a secure access code (SAC) or a Symantec VIP token to access certain high-risk events.
The following are examples of high-risk events and are subject to change.
Table 15. High-risk events
|
Event description |
Event as it appears in Q2 Console/Q2central |
|---|---|
|
Authorize an external transfer |
Authorize External |
|
Add a new user |
Create User Online |
|
Update a user profile |
Update a User Profile |
|
Edit secure access code (SAC) |
Edit Secure Access Code Target |
|
Delete secure access code (SAC) |
Delete Secure Access Code Target |
|
Edit security alert preferences |
Set Security Alert User Preferences |
|
Change of address form |
Add Change Address |
|
Disable date alerts |
Update Alert Date |
|
Disable account alerts |
Update Alert HADE Currency NoteHADEs refer to Host Account Detail Elements, which include transaction and account details from the core. |
|
Disable history alerts |
Update Alert Posted Transaction |
|
Disable transaction alerts |
Update Alert Online Activity |
For more information on Q2 Patrol as a product, see the Q2 Patrol CSR Reference Guide, located in the Q2 Patrol Product Documentation folder within the Q2 Customer Portal.