🗃️
PropScreen
  • PropScreen Overview
  • Introduction
    • The Problem
    • Problem Importance and Impact
    • Solution Overview
      • How Propscreen Addresses the Problem
      • Use Cases
      • User Personas
  • System Architecture
    • Core Components of Propscreen
      • PropScreen's Checks
      • Context Strings Database
      • Hashed Organizational Sensitive Information
      • Interdiction Log Database (Reports)
    • Architecture Overview
    • Sequence Diagrams by Use Case
      • Use Case 1 Sensitive Information Disclosure Interdiction
      • Use Case 2 Logging of Interdiction Events
  • Project Considerations
    • Threat Modeling
      • Key Threats
      • Key Threat 1
      • Key Threat 2
      • Key Threat 3
    • Secure by Design
    • Alternative Solutions
      • NER and Regex Based Scans
      • Traditional Data Loss Prevention
    • PropScreen's LLM Implementation
  • The Proof of Concept
    • Demo Video
    • Try the Proof of Concept
  • Going Forward...
    • SIEM Integration
    • Role Based Access Control Dependent Response Filtering
    • The Good, The Bad, and the Learning
Powered by GitBook
On this page
  1. Going Forward...

Role Based Access Control Dependent Response Filtering

PreviousSIEM IntegrationNextThe Good, The Bad, and the Learning

Last updated 9 months ago

The ability of PropScreen to filter responses based on the role a user has in their organization is another expansion of functionality slated for the next phase of development in the product. RBAC dependent response filtering is an extension of the and operates in the same manner. The main difference being that instead of a universal there would be separate databases that would contain the hashes of data that the user is not authorized to see based on their role. In other words, each role would have their own hashed database of sensitive organizational information that checks would be conducted against in the model responses.

database of organizational sensitive information
first use case