Zum Hauptinhalt springen

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​

NameTypeRequiredDescription
authorizedanyNoWhether the user is authorized
access_reasontextNoDocumented reason for data access
encrypted_at_restanyNoWhether data is encrypted at rest
encrypted_in_transitanyNoWhether data is encrypted in transit
audit_loggedanyNoWhether audit logging is enabled
user_roletextNoUser role for access control checks
access_scopetextNoScope of data access
consent_obtainedanyNoWhether user consent was obtained (GDPR)
data_age_daysanyNoAge of the data in days for retention checks
breach_detected_attextNoRFC3339 timestamp of breach detection

Output ports​

NameTypeRequiredDescription
resultjsonNoFull compliance check result with violations, warnings, and metadata
compliantbooleanNoWhether all checks passed
successbooleanNoWhether the compliance check completed successfully

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
FrameworkframeworkenumYeshipaahipaa, gdpr, sox, pci-dss, customCompliance framework to evaluate against
Check Typecheck_typeenumNodata_accessdata_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, allSpecific compliance check to perform

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Custom RulesrulesjsonNoArray of custom compliance rules (required for custom framework)
Retention Daysretention_daysnumberNo2555min 1; max 36500Maximum data retention period in days
Max Fieldsmax_fieldsnumberNo10min 1Maximum fields allowed for data minimization check

Errors​

CodeDescription
INVALID_FRAMEWORKThe specified compliance framework is not recognized
COMPLIANCE_VIOLATIONOne or more compliance checks failed with violations
MISSING_CUSTOM_RULESCustom 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.

Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..