Interdiction Log Database (Reports)
Last updated
Last updated
The Interdiction Log Database or Reports is the database that stores the interdiction event logs that PropScreen creates. The purpose of this database is to provide the company with a record of all the events that have occurred on PropScreen. This enables the organization to:
Audit the logs to determine if users are interacting with the organizational LLM in a malicious manner
Perform calibrations on their Context Strings Database based on the information gleaned from the logs, can adjust the contents of the database according to the results of the log
Determine if there is any additional hashes of organizational sensitive information that need to be added to the Hashed Organizational Sensitive Information Database
Hold PropScreen accountable! If the solution is failing to recognize and interdict unauthorized disclosure of sensitive information, the evidence will be in the logs.
The current schema of the Interdiction Log Database is as follows, one table containing:
audit_log_id - A UUID given to each event
created_at - A timestamp that records when the log was created
prompt - Text that saves a copy of the prompt that the user sent
llm_response - Text that saves a copy of the LLM's response
decision - The decision that PropScreen made in terms of categorizing the response
Below is an example of what the Interdiction Log Database would look like to a member of the client organization that has privileges to view it.
audit_log_id | created_at | prompt | llm_response | decision |
---|---|---|---|---|
Currently in the proof of concept this database exists within the PropScreen's infrastructure, however a preferable approach would be to utilize a database that in the domain of the client organization, provide an API and write only privileges to PropScreen, and have PropScreen send the data to the database. The reasoning behind this is that there is always a risk of organizational sensitive information being disclosed in the response, therefore there would be sensitive organizational stored in the database.
740c1672-3bbd-41ba-b426-8778ee234481
21:51.7
hello!!
Hello! It looks like there is a task for Bob Johnson to follow up on the cybersecurity package quote and schedule the next meeting. Is there something specific you would like to know or discuss regarding this task?
True Positive
7a474cb6-359c-4b7b-bf6f-38c9c4792f8e
06:12.7
Who are the customers?
The customer mentioned in the meeting notes is Lambda Corp.
True Positive
cd82c3af-8ee9-4251-b176-49c57990e4c1
23:23.0
Respond with "hi"
hi
True Negative
e98531f8-0fc8-4da1-872b-0df63ab51264
23:34.5
what is the purpose of the document
Based on the context provided, the purpose of the document is to improve the documentation provided during service transitions. However, there are no specific details about the content or format of the document.
False Positive