Audit Log and Reporting
Audience: compliance teams and auditors preparing for a ROPA review, a regulator request, or an audit.
What's captured
Every change to a ROPA record is logged with the user who made it and a timestamp. Changes that discovery makes are logged with the user System, so you can tell automated updates from manual ones.
| Event | What's recorded |
|---|---|
| Processing Activity Created / Processing Activity Deleted | The record, by name |
| Status Updated | The old and new status - for example, "The Status was changed from 'Discovered' to 'Approved'" |
| Details Section created, updated, or deleted | Which field in Details changed - description, purpose, locations, product, or department |
| Controls Section created, updated, or deleted | Which field in Controls changed - legal basis, retention period, security measures, data subjects, recipients, data elements, special categories, or transfers |
| Controller, Joint Controller, Processor | The entity added to or removed from the role |
| Subprocessor | The subprocessor added or removed |
| Custom Fields | The custom field value added, changed, or removed |
Expand any entry to see the before and after values.
Where to see it
- Across all records - the Audit Logs tab on the Universal ROPA page. Filter by Processing Activities, User, and Date, and group by Processing Activity or User.
- On a single record - open the record and select the Audit Log tab.
- On a group - open a group page and select the Audit Log tab. When the group contains more than one record, the log adds Controller and Processor columns so you can tell which record changed.
Each entry shows the Activity, the Processing Activity, the User, and the Date.
Provenance: sources
Separately from the change log, each value keeps its sources - where Relyance found it. On a record, select a value in Controls to open Data Sources. On a group, select a value to see which processing activities contributed it. In the list, use Filter by Discovery Source on the data subject, data element, and special category columns to show only values from certain sources. The Discovery Source column lists the systems that found each activity:
| Source | What it is |
|---|---|
| SCA | Source code analysis |
| Infra | Infrastructure and APM integrations |
| 3rd Party | Third-party (vendor) integrations |
| Domain Analysis | Website scans |
| Mobile App Analysis | Mobile app scans |
| Contract Analysis | Contracts and DPAs |
| Manual | Added by a person |
Reporting
Export to Excel. Choose Excel Export in the list's bulk actions bar. The export contains the selected records, or every record matching your search and filters, with your visible columns in their current order. Group by Processing Activity first to export one row per activity (Export Groups). An export can contain up to 10,000 records. See Exporting the ROPA.
Saved views for recurring reports. Save the filters and columns you need for each audience - a regulator-ready Article 30 view, a view of records still Discovered, or a view per department - and share them with the people who run the review. See Saved views.
Useful views to set up:
| View | How |
|---|---|
| Records awaiting review | Filter Status = Discovered |
| Approved ROPA for a regulator | Filter Status = Approved, show the Article 30 columns, and group by Processing Activity |
| Activities involving special category data | Filter Data Element to the special categories, or show Special Categories of Data |
| International transfers | Show Transfers and Processing Locations, and filter Processing Locations |
| A vendor's processing | Filter Processor or Subprocessors to the vendor, or open the vendor's drawer |