End-to-End Encrypted Pentest Reporting Your Findings Are Encrypted Before They Leave the Browser.

In Pental’s Portal each firm owns its data, in a database of its own, which Pental has no access to. The testing work in it is also end-to-end encrypted, so read straight from the database, it is unreadable: findings, evidence, files and the credentials clients send are encrypted in the browser of whoever writes them, and opened only in the browsers of the people allowed to read them. Nobody sets anything up.

66fields end-to-end encrypted
9tables of testing work
0keys at Pental that open it
0setup steps
Two Layers

Where the Work Is Kept, and What It Is While It Is There.

The first layer is where the data is kept. Each firm’s data is in a Postgres database the firm owns, in its own account and region, and Pental keeps no copy of it and has no way in. How your own database works.

The second is what that data is while it is there. Encryption at rest protects a stolen disk, but the server that holds the data holds the key to it as well. End-to-end encryption takes the key away from the server: the testing work is encrypted in the browser before it is sent, and opened only in your people’s browsers. A dump of your database, a backup of it, or anyone reading it, gets ciphertext.

Where it is kept
a database your firm owns
What it is there
ciphertext
Where it is opened
your people’s browsers
Pental holds
no copy, and no key that opens it
your browser encrypts→your database keeps ciphertext→your people’s browsers open it
What Is Encrypted

All of the Testing Work.

Everything that says what was found, and how, is encrypted. What runs the firm around it stays readable, so the parts of the portal that count, bill and schedule keep working.

  • Findings, in fullTitle, description, impact, remediation, affected assets, evidence and screenshots, references, CWE and category, retest results, your own fields, and the QA review’s remarks on them.
  • EngagementsScope and each phase’s scope, executive and retest summaries, caveats, notes, sections and their drafts, appendices, artifacts, and the text of the letter of attestation.
  • Every fileEvery file on an engagement, the reports among them, encrypted whole with its type, and opened when it is downloaded.
  • Around the workComments, the QA review, the timeline’s entries and the asset inventory, its owners and tags among it.
  • Credentials a client sendsEncrypted in the client’s own browser before they are sent, each value and each file.
  • What is being typedA finding a colleague has open sees what you are typing as you type it, encrypted on its way.
Readable, by Design

Client and engagement names, dates, statuses, severities and scores stay readable, as do your people and their roles, so the calendar, counts, dashboards and automation all work. Each engagement carries a badge saying it is end-to-end encrypted.

How the Keys Work

Kept by People and Their Browsers, and Opened by No Server Alone.

Each client has a key and the firm has one, and an engagement’s work is under its client’s. The database keeps every key only wrapped: sealed separately for each browser and each sign-in that may open it, so nothing it holds opens anything by itself.

Every browser a person signs in on makes a key of its own, which it can use but never hand out. A new browser is opened as the person signs in, by their password.

For the times a person has nothing of their own to open their work with, a first sign-in, a forgotten password, a browser that has lost its key, your database keeps each person a recovery key under two locks. The browser that makes it seals it to a key of Pental’s before your database is handed it, and your database seals that again under its own Vault. Your database gives it only to its own person, signed in with their second factor proved, and Pental’s server opens its half only for a ticket your database made for that sign-in. Neither opens it alone: your database has only what Pental sealed, and Pental is sent no data and no session.

Who may open which key is your database’s rule, beside the rest of its access rules: your administrators, seniors and testers every key, an external tester the keys of the clients they work on, and a client’s own people their own organisation’s. Someone who leaves, or whose role changes, keeps no key they are no longer allowed.

Keys
one for the firm, one for each client
A new browser
opened by the person’s password
A first sign-in, a reset password
a recovery key under two locks, your database’s and Pental’s
Who may open what
your database decides, by role
A client
its own key and no other
Nothing to Set Up

On for Every Firm, With No Key to Keep.

  • On from the first sign-inYour firm’s keys are made in the first administrator’s browser as they first sign in, so the work is encrypted from the first finding. Settings, Security says so.
  • No recovery key at setupNobody is asked to make, write down or keep a key. Recovery is automatic: a person’s password opens their work on a new browser, and a forgotten password is reset from the sign-in page, with the work open again at the next sign-in.
  • An optional recovery kitA person can also save a kit of 52 letters and numbers on their profile, which opens their work with nothing else: no browser of theirs, no password and neither lock. It is made in their browser, and neither Pental nor the database ever sees it.
  • Passkeys or authenticator appsEither works as the second factor, and neither holds a key: the password a person signs in with is what opens their keys.
  • One browser alone, flaggedWhere only one browser at the firm could open its work, the portal says so to the administrator, with what to do about it, so a lost laptop never locks the firm out.
Works With Your Tools

The Integrations, Handed Only What They Need, When They Need It.

  • Trackers, email, AI and copiesA ticket in a client’s tracker, an email that carries a finding, an AI draft, a copy in SharePoint or Google Drive and a send to a password manager are each handed the words they need by the browser that sends them, as they are sent. The copy of an email your database keeps is encrypted once it has gone.
  • Working togetherTwo people editing the same finding see each other’s changes live, encrypted on their way.
  • Imports and the APIScanner output imported in the browser is encrypted there. An API key made in the Portal opens what its person may read, and the API guide gives the steps a script follows.
  • Reports and documentsMade in the browser from the opened work, in your own Word template or the built-in PDF, and kept encrypted.
The Cryptography

Standard Primitives, in the Browser’s Own Web Crypto.

Nothing invented here: the browser’s built-in Web Crypto for every cipher, and Argon2id for stretching a password.

Data
AES-256-GCM, a fresh 96-bit IV for every value, the key’s id as associated data
Keys sealed for a browser
ECDH on P-256, HKDF-SHA-256, AES-256-GCM
A browser’s own key
P-256, made non-extractable by Web Crypto, kept in that browser
A password
Argon2id, 64 MiB, three passes
A recovery key
sealed to a key of Pental’s (ECDH on P-256, HKDF-SHA-256, AES-256-GCM), then under your database’s Vault
A recovery kit
256 random bits, written as 52 letters and numbers
Files
encrypted whole, with their type, under the key of the engagement’s client
Questions

Questions About End-to-End Encryption.

That the testing work is encrypted on the device of whoever writes it and opened only on the devices of the people allowed to read it. The servers in between, and the database that keeps it, hold ciphertext, and nothing they hold opens it by itself. In Pental’s Portal that covers findings, evidence, files, notes, comments and the credentials clients send.

No. It is on from your first sign-in. Nobody is asked to make, write down or keep a key: each browser makes its own, and a person’s password opens their work on a new one.

Their work is not lost with it: their password opens it on their next browser. Remove the lost browser on their profile, or under Settings, Security, and it is given no keys again, and sign its sessions out there too. If the password is forgotten too, it is reset from the sign-in page, and the work opens with the new one.

Yes, in their own portal. A client’s people are given their own organisation’s key and no other, so they read their engagements and nobody else’s. Their first sign-in opens it with nobody else online, and after that their password does.

Yes. An authenticator app and a passkey are both second factors and neither holds a key: the password a person signs in with opens their keys on a new browser, so either choice works with nothing extra to do.

They reset it from the sign-in page like any other, sign in with the new one and their second factor, and their work opens, on any browser and with nobody else online. A recovery key your database keeps for each person does it. It is under two locks, your database’s and Pental’s, so neither opens it alone.

Yes. Tracker tickets, emails, AI drafting, SharePoint and Google Drive copies and password managers are handed the words they need by the browser that sends them, as they are sent. An API key made in the Portal opens what its person may read, and the API guide gives the steps a script follows.

Encrypted From the First Finding.

Start a free trial: your portal is end-to-end encrypted from the moment it is live, on a database your firm owns.