All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Security Approaches for Granting LLMs Access to SSH and Database Systems

By

nico

4mo ago· 38 min readenNews

Summary

The article discusses approaches for safely granting Large Language Models (LLMs) access to sensitive systems like SSH and databases. It presents a solution where LLMs work with local development databases and output scripts that are version-controlled, audited, and reviewed before being run against production systems. The discussion emphasizes the importance of not giving LLMs direct access to Personally Identifiable Information (PII) and mentions tools like Microsoft's Presidio for redacting PII from production data before LLM processing. The conversation focuses on security best practices, risk mitigation, and practical implementation strategies for integrating LLMs into development workflows while maintaining security and compliance standards.

Key quotes

· 3 pulled
Our solve is to allow it to work with a local dev database and it's output is a script. Then that script gets checked into version control (auditable and reviewed). Then that script can be run against production.
Giving LLM even read access to PII is a big 'no' in my book.
On PII, if you need LLMs to work on production extracted data then https://github.com/microsoft/presidio is a pretty good tool to redact PII. Still needs a bit of an audit but as a first pass does a terrific job.
Snippet from the RSS feed
fhub 86 days ago | [–]

You might also wanna read