Skip to content

README.md

Latest commit

 

History

History
69 lines (49 loc) · 4.12 KB

README.md

File metadata and controls

69 lines (49 loc) · 4.12 KB

Securis - API

Backend for a secure document platform: Microsoft OAuth SSO, multi-strategy auth, SQL Server Dynamic Data Masking, a redacting logging interceptor, and a custom encryption + compression envelope for point-to-point payloads.

Problem

Institutional document workflows (oficios, memorandos) carry confidential fields, must survive audit, and need single sign-on against an existing Microsoft tenant. Plaintext fields in logs leak data; a single application user with full DB access defeats database-level confidentiality; a hand-rolled cipher alone isn't a credible security story. Securis layers four independent controls so each one carries its own piece of the model.

Approach

Four security layers, designed to compose:

  1. Microsoft OAuth + JWT. passport-microsoft authenticates against the Office 365 tenant; JWT is issued for downstream API calls. Local and JWT strategies are also wired for service accounts.
  2. Custom point-to-point envelope. Payloads in transit are wrapped in a Huffman-coded framing protocol shared with the frontend. Trees are generated by the huffman:generate CLI and split between a frontend↔backend tree (huffman-back) and a backend↔database tree (huffman-db).
  3. SQL Server Dynamic Data Masking. Two database principals (app_admin, app_user) are provisioned with different masking access - application traffic flows through the masked principal, administrative paths through the unmasked one. Field-level confidentiality is enforced at the database, not at the application.
  4. Redacting logging interceptor. Sensitive fields are stripped from logs before they leave the request pipeline, so audit retention doesn't undo (1)-(3).

The encryption + compression envelope sits inside this layered model - its role is point-to-point payload obfuscation between frontend and backend, with the integrated confidentiality story carried by MS OAuth + SQL Server DDM + redacting logs.

Stack

Layer Tech
Framework NestJS 11
Language TypeScript
ORM Prisma + @prisma/adapter-mssql
DB Microsoft SQL Server (with Dynamic Data Masking)
Auth passport-microsoft (MS OAuth) + JWT + local strategies
Mail @nestjs-modules/mailer + Nodemailer (password reset, document delivery)
PDF pdfkit + puppeteer + qrcode + pdf-password (electronic signatures)
Infra Docker / docker-compose

Highlights

  • Microsoft OAuth single sign-on (passport-microsoft), with JWT issuance for downstream calls
  • Document lifecycle modules (features/documents) for oficios and memorandos
  • Electronic signatures with QR codes; PDFs sealed via pdfkit + pdf-password
  • Encryption module with Clean Architecture layout (application / domain / infrastructure / presentation) and a huffman:generate CLI
  • SQL Server Dynamic Data Masking enforced at the data layer via two distinct DB principals
  • Redacting logging interceptor (audit-safe logs)
  • Shared point-to-point envelope protocol with the frontend (devjaes/securis-web)

Local setup

pnpm install
cp .env.example .env       # MS OAuth keys + MSSQL connection + JWT secret
pnpm huffman:generate      # produce huffman-back / huffman-db trees
docker compose up -d       # SQL Server + dependencies
pnpm dev                   # nest start --watch

Useful env vars: DB_SERVER, DB_PORT (1433), DB_NAME, separate DB_USER_ADMIN / DB_USER (DDM split), MICROSOFT_CLIENT_ID/SECRET/TENANT_ID, JWT_SECRET, HUFFMAN_TREE_BACK_PATH, HUFFMAN_TREE_DB_PATH.

Status & limitations

  • University capstone project. Single Microsoft tenant.
  • No public demo (institutional auth required).
  • Default branch is develop (active integration). main is held back for releases.

Team & my role

  • My role: Lead Architect - system design, the four-layer security model, MS OAuth + DDM integration, project leadership.
  • Contributors: Pablo Martinez (@SrPabvliss), Daniel Zhu (@Chu2409).
  • Frontend repo: devjaes/securis-web

Portfolio

Project entry on devjaes.dev