🗃️
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. Project Considerations
  2. Alternative Solutions

Traditional Data Loss Prevention

PropScreen plays a enhances Data Loss Prevention (DLP) efforts by implementing best practices for the use of Generative AI, particularly with Large Language Models (LLMs). DLP is a set of tools and processes used to ensure that sensitive data is not lost, misused, or accessed by unauthorized users. DLP software detects potential data breaches and prevents them by monitoring, detecting, and blocking sensitive data while in use (endpoint actions), in motion (network traffic), and at rest (data storage). PropScreen is dedicated to safeguarding proprietary company-sensitive information and personally identifiable information (PII) by employing robust security measures. These include encrypted web traffic between the user and the language model, hashed data at rest within hashed databases, and the implementation of fuzzing techniques in our code and storage containers. Challenges with DLP, such as false positives and negatives, are addressed by PropScreen through meticulous logging on a prompt-to-prompt basis. This includes alerting security teams and auditors about the user's interaction with the language model, the given prompt, the received response from the LLM, and any flags triggered by the response.

PropScreen differs from traditional DLP solutions because its sole focus is on the traffic that occurs between a client and the company’s LLM, an entirely internal process. Traditional DLP methods tend to focus on the edges of a network in order to prevent the exfiltration of sensitive information from their network. PropScreen does not replace traditional DLP approaches, but enhances the existing DLP regime by adding an additional layer of security between the client application and model that does not inference with the organizations existing DLP architecture.

PreviousNER and Regex Based ScansNextPropScreen's LLM Implementation

Last updated 9 months ago