Skip to content

Control 2.4: Information Barriers for Copilot (Chinese Wall) — Verification & Testing

Test cases and evidence collection for validating Information Barrier enforcement with Copilot.

Test Cases

Test 1: Barrier Enforcement in Teams Communication

  • Objective: Verify users in blocked segments cannot communicate via Teams
  • Steps:
  • Identify test users in the Investment Banking and Research segments
  • As the IB user, attempt to start a Teams chat with the Research user
  • Verify the chat is blocked with an appropriate message
  • Verify the block event is logged
  • Expected Result: Communication blocked with clear policy notification
  • Evidence: Screenshot of block notification and audit log

Test 2: Copilot Content Grounding Barrier

  • Objective: Verify Copilot does not ground responses on content from blocked segments
  • Steps:
  • Create unique test content accessible only within the Research segment
  • As an Investment Banking user, ask Copilot a question that would require the Research content
  • Verify Copilot does not reference or include Research segment content
  • As a Research user, verify the same Copilot query does return the content
  • Expected Result: Copilot respects barrier boundaries in content grounding
  • Evidence: Copilot responses from both segments showing barrier enforcement

Test 3: SharePoint Barrier Enforcement

  • Objective: Confirm barriers prevent cross-segment content discovery in SharePoint
  • Steps:
  • Verify a SharePoint site owned by the Research segment is not searchable by IB users
  • Perform a SharePoint search as an IB user for content known to be in Research sites
  • Verify no results from Research segment sites appear
  • Expected Result: SharePoint search respects barrier boundaries
  • Evidence: Search result screenshots from barred user

Test 4: Barrier Exception Validation

  • Objective: Verify approved barrier exceptions function correctly
  • Steps:
  • Configure a documented exception (e.g., Compliance team can access both segments)
  • As a Compliance team member, verify access to both IB and Research content
  • Verify the exception is limited to the approved scope
  • Confirm exception documentation is current with governance approval
  • Expected Result: Exceptions work as configured with proper documentation
  • Evidence: Exception configuration and access verification

Test 5: Channel Agent IB Coverage Verification

  • Objective: Confirm Channel Agent deployments comply with the IB gap compensating controls
  • Steps:
  • Enumerate all active Channel Agent deployments: navigate to Microsoft 365 Admin Center > Agents > All agents / Registry or Microsoft Teams Admin Center > Teams apps
  • For each Channel Agent, retrieve the channels where it is deployed
  • Review the membership of each channel where Channel Agent is deployed
  • Confirm no channel with an active Channel Agent has members from IB-separated segments
  • Verify the Channel Agent IB limitation is documented in the firm's supervisory procedures
  • If sensitivity labels are applied as a compensating control, confirm labeled content in IB-adjacent channels is not accessible via Channel Agent
  • Expected Result: No Channel Agent is deployed in a channel containing members from IB-separated segments; IB limitation is documented in supervisory procedures
  • Evidence: Channel Agent deployment list; channel membership review; supervisory procedure documentation

Test 6: IB Coverage Matrix Completeness

  • Objective: Verify the IB coverage matrix reflects the actual enforcement status of all Copilot surfaces
  • Steps:
  • For each Copilot surface in the control's coverage matrix, perform a functional test from a user in one IB segment to access content from a barrier-separated segment
  • Confirm Microsoft Copilot Chat, Word, Excel, PowerPoint, and Teams Copilot scenarios respect SharePoint/OneDrive and Teams barrier test content where those workloads enforce IB
  • Confirm Outlook/email separation is handled by approved non-IB controls if the firm's wall design requires email restrictions
  • Confirm Copilot Pages, Copilot Notebooks, Channel Agent, and embedded-file agent knowledge are treated as unsupported/limited for IB rather than assumed covered
  • Document test results against the coverage matrix
  • Expected Result: Supported workload-backed Copilot scenarios pass functional testing; unsupported or limited surfaces are disabled, scoped, or separately controlled
  • Evidence: Functional test results for each Copilot surface

Evidence Collection

Evidence Item Format Storage Location Retention
Barrier policy configuration CSV Compliance evidence repository 7 years
Barrier enforcement test results PDF with screenshots Compliance evidence repository 7 years
Copilot barrier test results PDF Compliance evidence repository 7 years
Exception documentation and approval PDF Governance document repository 7 years

Compliance Mapping

Regulation Requirement How This Control Supports It
FINRA Rule 5280 Information barriers for trading Barriers can support firm-approved trading information wall controls where Legal/Compliance determines the rule applies
SEC Regulation FD Fair disclosure requirements Information barriers can help reduce selective-disclosure risk where Legal/Compliance determines the use case is in scope
Securities Exchange Act Section 15(f) Broker-dealer information barriers Barriers can support firm-approved broker-dealer information wall procedures where applicable
MiFID II Conflict of interest management Information barriers can support firm-approved conflict management controls where applicable
- Back to Control 2.4