Docs

FC-ANY-PII-001: PII access without audit log

Workflow processes PII-named variable but contains no Log Message activity.

criticalpiiuipath

What it detects

Workflow processes PII-named variable but contains no Log Message activity. Flowcerta surfaces this finding from the active validation pipeline for supported file types and platforms.

Why it matters

PII findings matter because workflow automations regularly touch regulated identifiers, customer records, and health data. Weak auditability or unsafe logging turns ordinary bot activity into a compliance exposure.

Example violation

Workflow processes PII-named variable but contains no Log Message activity.

Fix guidance

UiPath

  • Add LogMessage activities before and after PII access. Do not log the PII value itself.
  • Use platform-native assets, credentials, bounded retries, and Log Message checkpoints instead of hardcoded literals or silent failure paths.
  • Revalidate the workflow after the change and confirm the finding no longer appears.

Verification steps

  1. Run validation again and confirm the rule no longer appears in the finding list.
  2. Review the changed workflow artifact directly to verify the risky pattern is gone.
  3. Capture the new validation result as evidence for the relevant owner or compliance review.

Compliance references

Related rules

FC-ANY-PII-002FC-ANY-PII-003

This page is generated from the canonical Flowcerta rule registry used by validation scoring.

Browse all rule playbooks