Compliance
Category: Security
Node id: compliance
Standards: HIPAA, SOC2, GDPR
Enforces compliance policies and validates data against HIPAA, GDPR, SOX, PCI-DSS, and custom frameworks
What it does
- Five frameworks: HIPAA, GDPR, SOX, PCI-DSS, custom
- 14 check types including data access, retention, encryption, and breach notification
- Custom compliance rules for organization-specific policies
- Violation and warning reporting with detailed explanations
- GDPR-specific checks: consent, data portability, right to erasure, data minimization
Use cases
- Validate HIPAA compliance before processing PHI data
- Check GDPR consent and data subject rights compliance
- Enforce data retention policies across pipeline workflows
- Run comprehensive compliance audits with the 'all' check type
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
authorized | any | No | Whether the user is authorized |
access_reason | text | No | Documented reason for data access |
encrypted_at_rest | any | No | Whether data is encrypted at rest |
encrypted_in_transit | any | No | Whether data is encrypted in transit |
audit_logged | any | No | Whether audit logging is enabled |
user_role | text | No | User role for access control checks |
access_scope | text | No | Scope of data access |
consent_obtained | any | No | Whether user consent was obtained (GDPR) |
data_age_days | any | No | Age of the data in days for retention checks |
breach_detected_at | text | No | RFC3339 timestamp of breach detection |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Full compliance check result with violations, warnings, and metadata |
compliant | boolean | No | Whether all checks passed |
success | boolean | No | Whether the compliance check completed successfully |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Framework | framework | enum | Yes | hipaa | hipaa, gdpr, sox, pci-dss, custom | Compliance framework to evaluate against |
| Check Type | check_type | enum | No | data_access | data_access, data_retention, encryption, audit_trail, access_control, phi_handling, breach_notification, data_subject_rights, consent, data_portability, right_to_erasure, data_minimization, data_integrity, all | Specific compliance check to perform |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Custom Rules | rules | json | No | Array of custom compliance rules (required for custom framework) | ||
| Retention Days | retention_days | number | No | 2555 | min 1; max 36500 | Maximum data retention period in days |
| Max Fields | max_fields | number | No | 10 | min 1 | Maximum fields allowed for data minimization check |
Errors
| Code | Description |
|---|---|
INVALID_FRAMEWORK | The specified compliance framework is not recognized |
COMPLIANCE_VIOLATION | One or more compliance checks failed with violations |
MISSING_CUSTOM_RULES | Custom framework requires rules array configuration |
Runtime notes
- compliant is true only when violations is empty — success indicates the check ran without errors, not that compliance passed
- HIPAA checks look for boolean inputs (authorized, encrypted_at_rest, etc.) — missing inputs are treated as non-compliant
- Use check_type='all' to run every check for the selected framework in a single execution
- Each violation includes a rule reference (e.g., HIPAA-164.308) and severity — wire to an audit node for compliance logging
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.