The key concept is that once the entity has one database
analysed and knows it to be compliant to relevant standards,
it can use that as a master profile, configuring its CAATs tool
to compare the profiles of interest across all of its Oracle
databases. This can be done by joining on the fields profile
and resource (or simply on resource), displaying all records
where the limit is not equal. For example, the failed login
attempts may differ across a sample of databases. In this
manner, the entity can quickly flag noncompliant profiles for
follow-up and review.