Collaborative DLP Access Blocking with Content-Based Permission Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data loss prevention (DLP) systems in collaborative environments struggle to effectively block access to sensitive information and manage user interactions to ensure compliance with organizational policies.

Innovation Solution

Implementing access blocking as part of DLP within collaborative services, where actions on content are evaluated against policy rules, activating block access tags, ignoring or applying constraints to permissions, and restricting access to predefined users, with user interactions to manage and override restrictions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access blocking is implemented to restrict access to sensitive content, then security is improved, but user accessibility and ease of operation deteriorate

Engineering Contradiction:
ImprovesecurityVSAvoiduser accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies access blocking selectively and locally - only to specific content items that match DLP policy criteria, rather than applying blanket restrictions. The block access tag is activated only for content containing sensitive information, allowing users to freely access content that does not violate policies while restricting access only where necessary for security.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system segments user access rights by applying different permission levels to different content items. Users retain their previously defined permissions for content without block access tags, while content with activated block access tags receives restricted access. This segmentation allows simultaneous maintenance of security restrictions and user accessibility without one undermining the other.

Inventive Principle:
Principle #1Segmentation

2Reliability

If DLP policy rules are strictly enforced to prevent data loss, then compliance is improved, but productivity and ease of operation worsen due to increased restrictions

Engineering Contradiction:
ImprovecomplianceVSAvoiduser efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary evaluation of content against DLP policy rules before access is granted. The block access tag is activated in advance based on content analysis, so that when users attempt to access content, the restriction is already in place rather than being imposed during the access attempt. This prevents productivity loss from repeated access denials.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically evaluates content and applies access blocking without requiring manual intervention from users or administrators. The DLP module autonomously detects sensitive information, activates block access tags, and enforces restrictions based on policy rules, eliminating the need for users to manually check compliance and reducing productivity impacts.

Inventive Principle:
Principle #25Self-service

3Reliability

If automated detection and blocking is implemented, then security monitoring is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity monitoringVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The collaborative service system performs multiple functions through its existing infrastructure - content processing, user authentication, and now DLP policy enforcement. The system leverages existing components to evaluate content and enforce access restrictions, avoiding the need for entirely separate specialized systems and reducing overall complexity despite enhanced security monitoring capabilities.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The block access tag serves as an intermediary mechanism between the DLP policy evaluation system and the content access system. Rather than requiring complex direct integration between security monitoring and access control systems, the block access tag acts as a simple flag that mediates between policy decisions and actual access enforcement, simplifying system architecture.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3210175B1Access blocking for data loss prevention in collaborative environments
Publication Date: 2025.08.13 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3210175B1 patent drawingFigure 1
  • EP3210175B1 patent drawingFigure 2
  • EP3210175B1 patent drawingFigure 3

AI summary

Data loss prevention (DLP) systems may be implemented in conjunction with collaborative services that may be integrated with or work in coordination with productivity services. Administrators may be enabled to configure DLP policies in the collaborative service to mitigate their organization's information disclosure risks, along with the detection and remediation of sensitive information. Access blocking may be one feature of the DLP system, where provision of access blocking may include determining if a detected action associated with content processed by the collaborative service matches access blocking criteria defined by DLP policy rules. In response to the determination that the action matches at least one access blocking criterion defined by the DLP policy rules, a block access tag associated with the content may be activated, previously defined permissions associated with the content may be ignored or altered, and access to the content may be restricted to a number of predefined users.