Advanced Cloud Security Documentation
Index

Compliance Overview

The Compliance module in Advanced Cloud Security provides field change tracking, approval workflows, and audit logging for sensitive data. This guide introduces the compliance features and how they work together.

What is the Compliance Module?

The Compliance module allows you to:

  • Track changes to designated fields
  • Require approval before changes are saved
  • Log all modifications for audit purposes
  • Notify approvers of pending requests
  • Enforce controls on sensitive data changes

Compliance License Requirement

The Compliance module requires the Security + Compliance license tier:

License Type Security Features Compliance Module
Security Only ✓ ✗
Security + Compliance ✓ ✓

Check your license status in ACS Setup.

How Compliance Works

Change Detection

When a user modifies a compliance-tracked field:

User Changes Field Value
         ↓
ACS Detects Change
         ↓
Captures: Old Value, New Value, User, Timestamp
         ↓
Evaluates: Is Approval Required?

Approval Workflow

If approval is required:

Change Captured
      ↓
Approval Request Created
      ↓
Approver Notified (Email)
      ↓
Approver Reviews
      ↓
Approve → Change Saved
Reject → Change Discarded

Logging

All compliance events are logged:

  • Change attempts
  • Approval requests
  • Approvals/Rejections
  • Who did what, when

Compliance Components

Component Purpose
Compliance Tables Select which tables to track
Compliance Setup Configure which fields need approval
Approval Rules Define approval workflows
Approvers Designate who can approve
Approver Groups Create approval groups
Compliance Log Audit trail of all events

Setting Up Compliance

Phase 1: Build (Setup Tables)

  1. Open Compliance Tables in Build phase
  2. Select tables containing sensitive fields
  3. Configure page associations
  4. Regenerate the extension

Phase 2: Configure

  1. Open Compliance Setup
  2. Configure which fields require approval
  3. Create Approval Rules
  4. Designate Approvers and Groups

No Extension Needed for Phase 2

Unlike security features, compliance configuration changes take effect immediately without extension regeneration.

Common Compliance Scenarios

Scenario 1: Vendor Bank Account Protection

Track and require approval for vendor banking changes:

Table Field Approval Required
Vendor Bank Account No. Yes
Vendor IBAN Yes
Vendor SWIFT Code Yes

Prevents unauthorized bank account modifications.

Scenario 2: Customer Credit Limit Control

Track credit limit changes:

Table Field Approval Required
Customer Credit Limit (LCY) Yes (if > 50,000)

High credit limits require finance approval.

Scenario 3: Employee Data Privacy

Track sensitive employee changes:

Table Field Approval Required
Employee Bank Account No. Yes
Employee Social Security No. Yes

All changes logged, approval required.

Tracking vs. Approval

You can configure fields for different levels of compliance:

Track Changes Approval Required Behavior
Yes No Log changes, save immediately
Yes Yes Log changes, require approval
No N/A No compliance tracking

When to Track Only

  • Audit requirement but no business need for approval
  • Low-risk fields that need history
  • Monitoring without interrupting workflow

When to Require Approval

  • High-risk changes (bank accounts, credit limits)
  • Segregation of duties requirements
  • Regulatory compliance requirements

The Approval Experience

For Users

When modifying an approval-required field:

  1. User enters new value
  2. System indicates approval is needed
  3. User confirms the change request
  4. Change is held pending approval
  5. User notified when approved/rejected

For Approvers

When approval is requested:

  1. Approver receives email notification
  2. Opens the approval request in BC
  3. Reviews old value, new value, requester
  4. Approves or rejects with comments
  5. Requester is notified of decision

Compliance Log

All compliance activity is logged:

Logged Information Purpose
Table and field What was changed
Old value Previous value
New value Requested value
User Who made the change
Timestamp When change was attempted
Approval status Approved, rejected, pending
Approver Who approved/rejected

Using the Log

  • Audit reviews
  • Compliance reporting
  • Investigation of issues
  • Regulatory evidence

Notifications

Email notifications keep stakeholders informed:

Event Notification To
New approval request Assigned approvers
Pending reminder Assigned approvers
Request approved Original requester
Request rejected Original requester
Escalation Escalation target

Configuring Notifications

In ACS Setup:

  • Sender name and email
  • Email body templates
  • Reminder frequency
  • Escalation settings

Best Practices

Start Small

  • Begin with highest-risk fields
  • Expand coverage over time
  • Learn from initial implementation

Define Clear Approval Paths

  • Designate appropriate approvers
  • Use groups for coverage
  • Set escalation for SLA

Monitor and Adjust

  • Review compliance log regularly
  • Adjust rules based on experience
  • Balance security with usability

Document Your Configuration

  • Record which fields are tracked
  • Document approval rules
  • Maintain approver list
  • Regular reviews