Skip to content

Latest commit

 

History

History
29 lines (23 loc) · 1.51 KB

pii.rst

File metadata and controls

29 lines (23 loc) · 1.51 KB
Raw

PII FIELDS

POSSIBLE ACTIONS RELATED TO PII

  1. Echo - scripts that run on AWS and scan uploaded resources for PII. The results are pushed back to CKAN
    • sets the pii_report_flag field to "OK", "FINDINGS", "EXCEPTION"
    • sets the pii_report_id field to the log path of the log file
    • sets the pii_timestamp field to current time in ISO without Z (without timezone)
    • sets the pii_predict_score field to the calculated score
  2. Resource Creation - when creating a resource from the UI the maintainer can specify whether the resource contains PII. If the user checks the checkbox then the dataset cannot be saved. Otherwise, if the checkbox is left unchecked, the pii field is set to the value "false"
  3. QA Dashboad
    1. Run PII Check (resource level, in the menu) - runs the Echo scripts
    2. Confirm Risk Classification (resource level, there is a "Confirm" link) - sets the pii_is_sensitive field
    3. Confirm Not Sensitive (dataset level, in the menu) - sets the pii_is_sensitive fields to false all resources in the dataset

DATASET PII FIELDS

  1. pii - manually set by Resource creation UI (set from js)
  2. pii_report_flag - set by Echo
  3. pii_report_id - set by Echo
  4. pii_timestamp - set by Echo
  5. pii_predict_score - set by Echo
  6. pii_is_sensitive - manually set by QA Dashboard / Confirm Risk Classification OR by QA Dashboard / Confirm Not Sensitive