1. DAVID Auditing cf

2. TOPICS Auditing Requirements per the Memorandum of Understanding (MOU) HSMV Auditing Process Auditing features in DAVID Best Practices Reports 2

3. Requirements 3

4. 4

5. 5

6. 6

7. 7

8. Misuse Requirements If misuse is identified you must submit the following information to Chief of Records at 2900 Apalachee Parkway, MS89, Tallahassee, FL 32399-0500: 1.Brief summary of the incident on agency letterhead 2.Number of records compromised 3.Were the owners of the compromised records notified? 4.If not, advise when you will be notifying them pursuant to 501.171 F.S. (SB 1524). 5.What disciplinary action (if any) took place due to this misuse? 6.How does your agency plan to mitigate future DAVID misuse? 8

9. Auditing Functions in DAVID 9

10. Audit Functions 10 Audit Functions User Activity Tab NOTE: Start Dates and End Dates are required fields

11. Audit Function 11

12. 12 Audit Reports

13. 13 Audit Reports

14. 14 Audit Reports

15. Audit Limitations Multiple Names – Refine your search to include social security number or driver license number etc. Minimum of 30,000 inquiries. 15

16. REPORTS 16 Reports

17. REPORTS 17 Reports

18. Monthly Summary 18

19. User Status History Report 19

20. User Status History Report 20

21. Agency Reports 21

22. Agency POC Report 22

23. Agency Reports 23

24. Agency User By Status Report 24

25. Agency Reports 25

26. User by Agency Report 26

27. Best Practices Audit reports should be conducted on different members on a regular basis. ECI use should be monitored/audited for compliance with statute. Consistent policies regarding change of employment status for user. (POC’s need to know when to immediately terminate access) Back up POC’s should always be in place. POC’s should work with Supervisors for appropriate roles of users. Auditing should consist of users that have activity to review. 27

28. Questions? www.flhsmv.gov/courts 28