Skip to content
Skills Library
Law & compliance · Learning & explanation

docs-security-overview

/docs-security-overview

Use when a prospect, customer, IT/security team, or procurement evaluator asks about Louis's security posture, data handling practices, compliance certifications, or infrastructure protections. Covers encryption standards, tenant isolation, access controls, certification roadmap (SOC 2, ISO 27001), no-training defaults, and zero-trust architecture. Applicable to all enterprise and regulated-sector deployments across all jurisdictions.

Licence
MIT
Last repository change
14.05.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a prospect, customer, IT/security team, or procurement evaluator asks about Louis's security posture, data handling practices, compliance certifications, or infrastructure protections. Covers encryption standards, tenant isolation, access controls, certification roadmap (SOC 2, ISO 27001), no-training defaults, and zero-trust architecture. Applicable to all enterprise and regulated-sector deployments across all jurisdictions.

Original author description

Use when a prospect, customer, IT/security team, or procurement evaluator asks about Louis's security posture, data handling practices, compliance certifications, or infrastructure protections. Covers encryption standards, tenant isolation, access controls, certification roadmap (SOC 2, ISO 27001), no-training defaults, and zero-trust architecture. Applicable to all enterprise and regulated-sector deployments across all jurisdictions.

How it works

  1. Purpose
  2. Certification roadmap
  3. Data encryption
  4. Tenant isolation
  5. Training data policy — no-training default
  6. Access controls
  7. Infrastructure security
  8. Data residency
  9. Legal-sector specific protections
  10. Penetration testing and audits
Original SKILL.md headings · 106 lines, 834 words
SKILL.md preview
---
name: docs-security-overview
description: Use when a prospect, customer, IT/security team, or procurement evaluator asks about Louis's security posture, data handling practices, compliance certifications, or infrastructure protections. Covers encryption standards, tenant isolation, access controls, certification roadmap (SOC 2, ISO 27001), no-training defaults, and zero-trust architecture. Applicable to all enterprise and regulated-sector deployments across all jurisdictions.
license: MIT
metadata:
  id: docs.security-overview
  category: docs
  jurisdictions: [__multi__]
  priority: P2
  intent: [security, data protection, compliance certifications, encryption, enterprise]
  related: [docs-tenant-isolation-explainer, docs-sso-saml-setup, docs-team-roles-permissions, docs-terms-of-service-summary]
  source: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)
  version: "1.0"
---

# Security Overview — Louis Legal AI Platform

## Purpose

This document answers the security questions that enterprise procurement, IT, and compliance teams ask before deploying a legal AI platform. It is designed to be shared directly with prospects or used as a briefing sheet for sales and customer-success teams.

## Certification roadmap

| Framework | Status | Target |
|---|---|---|
| SOC 2 Type II | In preparation | 2026 |
| ISO 27001 | In preparation | 2026 |
| Penetration testing | Annual third-party pentest | Ongoing |
| GDPR Article 28 DPA | Available on request | Now |
| UAE PDPL compliance | Under review | 2025 |

> Note: Certification timelines are targets and subject to audit completion. Customers requiring current certifications should request the latest status letter from their account manager.

## Data encryption

### At rest
- **AES-256** encryption for all stored data, including documents, conversation history, and generated outputs.
- Encryption keys are managed per-tenant via a Key Management Service (KMS); customer-managed keys (BYOK) available on Enterprise tier.
- Database-level encryption applies to all Postgres-hosted data; backup snapshots are also encrypted.

### In transit
- **TLS 1.3** for all client-server and service-to-service communication.
- Older TLS versions (1.0, 1.1) are disabled. TLS 1.2 retained only where strictly required for legacy IdP compatibility.
- HSTS enforced on all web endpoints; certificate pinning on mobile clients.

## Tenant isolation

Each customer organization is a logically isolated tenant:

- **Row-Level Security (RLS)** applied at the Postgres layer so no query can return rows belonging to another tenant even if application code were to malfunction.
- **Dedicated KMS keys per tenant** — a compromise of one tenant's key does not expose others.
- **No cross-tenant data sharing** — AI models do not see or learn from other tenants' documents.
- Admin tooling requires **dual-control authorization** for any action that crosses tenant boundaries.

See [[docs-tenant-isolation-explainer]] for the technical deep-dive.

## Training data policy — no-training default

By default, **customer documents are never used to train or fine-tune AI models**. This is a contractual commitment, not just a configuration option. Enterprise DPAs include an explicit prohibition on training use. For customers requiring further assurance, a Data Processing Agreement (DPA) is available that codifies this obligation.

## Access controls

### Zero-trust architecture
- No implicit trust based on network location; all requests require authentication and authorization.
- Service-to-service calls use short-lived tokens with least-privilege scopes.
- Administrative access to production infrastructure requires MFA, short-lived credentials, and audit logging of every action.

### User authentication
- Email + password (bcrypt-hashed, salted) as baseline.
- MFA (TOTP / hardware key) available on all plans; required on Enterprise.
- SSO via SAML 2.0 supported — see [[docs-sso-saml-setup]] for setup.

### Role-based access
- Five platform roles: Admin, Billing Admin, Lawyer, Paralegal, Viewer.
- Custom roles on Enterprise tier.
- See [[docs-team-roles-permissions]] for the full permissions matrix.

## Infrastructure security

| Control | Detail |
|---|---|
| Hosting | Managed cloud infrastructure (AWS primary region; region selection available for data-residency requirements) |
| Network | VPC isolation, private subnets for data tier, WAF on public endpoints |
| Secrets management | All credentials and API keys in a secrets manager; never in environment variables or code |
| Logging | Centralized audit log with tamper-resistant storage; customer-accessible activity log in-product |
| Incident response | Documented IR plan; customer notification within 72 hours of confirmed breach (GDPR and UAE PDPL aligned) |
| Vulnerability management | CVE scanning on all dependencies; critical patches within 24 hours; high-severity within 7 days |
| Backup | Daily encrypted backups with point-in-time recovery; tested quarterly |

## Data residency

- Default region: EU (Frankfurt) or UAE (depending on tenant's selected region at onboarding).
- MENA customers may request UAE-only data residency to satisfy UAE Federal Law on Data Protection, Saudi PDPL, or Lebanese preferences.
- Cross-border data transfer: covered by standard contractual clauses (EU SCCs) or equivalent where required.

## Legal-sector specific protections

- Attorney-client privilege considerations: Louis does not index or share contents of uploaded documents with any third party other than the AI model provider under a sub-processor DPA.
- Bar association technology guidelines: customers should independently verify that use of cloud-hosted AI services complies with their jurisdiction's professional responsibility rules (notably Lebanese Bar, DIFC Courts practice direction on AI, UAE Ministry of Justice guidelines).

## Penetration testing and audits

- Annual third-party penetration test by a qualified security firm.
- Summary pen-test reports available to Enterprise customers under NDA.
- Customers with specific compliance requirements (banking, insurance, DFSA-regulated entities) may request custom security assessments.

## How to use this overview

- **Sales calls**: share the encryption and no-training sections first — these answer 80% of initial objections.
- **IT/security review**: provide the full document plus the DPA template.
- **Procurement questionnaires**: map each question to the relevant section; for gaps, escalate to security@haqq.ai.

## Related skills

- [[docs-tenant-isolation-explainer]]
- [[docs-sso-saml-setup]]
- [[docs-team-roles-permissions]]
- [[docs-terms-of-service-summary]]
- [[docs-roi-calculator]]

Versions

The database has no other skills named docs-security-overview.

Database snapshot: 13.11.2026 · package version e6453b80e83b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100docs-tenant-isolation-explainer
    Use when a customer's security team, DPO, or IT architect asks how Louis prevents one law firm's data from being accessible to another, or how the platform enforces data separation at the infrastructure level. Explains the multi-tenant architecture: per-tenant Postgres row-level…
  • 90justice-intent-security-compliance
    Use when the public-facing assistant detects that a user — typically a procurement officer, law firm IT lead, in-house counsel, or compliance officer — is asking about data security, privacy compliance, data residency, SOC 2, GDPR, PDPL, or other regulatory requirements before…
  • 100soc2-prep
    When the user needs to prepare for SOC 2, build a compliance roadmap, assess security posture, quantify security risk, or says "we need SOC 2", "security audit", "compliance", "enterprise customer wants SOC 2", "CISO advice".
  • 90compliance-cert-planner
    Plan and sequence security and privacy compliance certifications (SOC 2, ISO 27001, GDPR, HIPAA, PCI DSS, CASA, etc.). Use when the user needs to scope which frameworks apply, classify each one, identify shared controls, and produce a roadmap.
  • 90security-architecture
    Security architecture: JWT rotation, OAuth2/OIDC, encryption, OWASP top 10, zero-trust patterns, mTLS, RLS multi-tenancy. Use when designing auth or security.
  • 100saas-trust-and-compliance-credentials-section
    Use when a SaaS proposal needs an evidence-qualified trust and compliance section covering security, privacy, certifications, sub-processors, continuity, audit posture, insurance, and exit; use the procurement skill to manage questionnaire and negotiation workflow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.