000034656 - User Change History Data Retention and CRE Table Cleanup in RSA Adaptive Authentication (OnPrem) 7.x

Document created by RSA Customer Support Employee on Jan 11, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034656
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Product/Service Type: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.x
 
IssueA Customer had questions around database cleanup activity and the data retention period of the UserChangeHistory table.
ResolutionAnswer:  Data is retained in the UserChangeHistory table indefinitely, i.e., from the time/date an AA instance is first installed and brought online.  There does not appear to be any cleanup on this table.
The Scheduler run nightly Offline Tasks are designed to clean up the following tables within the stated guidelines:
  • Desktops and Bindings tables are cleaned up based on last accessed and number of bindings retention parameters which are set in Back Office configuration screens.
  • The tables related to the Risk Engine and nightly Bayesian scoring tasks are cleaned up by removing data older than the previous 7, 30 or 90 days for a given table respectively.  Some of the CRE tables are listed below (-please note that this list is not exhaustive):
RE_TASK_STATUS table
RBA_BS_CATEGORY_BUCKET_STAT table
HC_CHALLENGE_RATE table
HC_EVENT_DISTRIBUTION table
HC_NORMALIZATION table
RBA_SCORE_NORMALIZE_STAT
ENTITY_AGGREGATIONS table
REOT_BUCKET_AGGR_STATUS table
REOT_EVENT_EXTRA_DATA table
REOT_EVENT_DYNAMIC_BUCKETS table
REOT_EVENT_STATIC_BUCKETS table

  • The exception to this would be the Event Log table wherein data is retained for 180 days.  

Attachments

    Outcomes