Credentials should never become test artifacts.
How Locus masks, encrypts, injects and redacts the secrets tests need.
Step 3 of a sign-in test, as stored
fill input[name="password"]
-
Value in the test definition
{{staging_admin_password}} - Value in the vault Encrypted, write-only, scoped to this site
- Value in the recording Masked Not in any recording batch
-
Value in captured network data
[REDACTED]
{"password": "[REDACTED]"}
Decrypted for this run only, typed from memory as the step executes.
From keystroke to replay
A secret is needed at one moment, in one place. Each stage keeps it out of the next.
Capture
The snippet masks password-field keystrokes and leaves them out of raw recording batches, in the browser.
Store
Credentials live in a per-site vault, encrypted with AES-256-GCM under a per-organization key, wrapped by a key-encryption key held in OpenBao.
Reference
Test definitions name a secret, such as
{{staging_admin_password}}, never its value.Inject
At execution, the runner that claimed the run receives the values it references and holds them in memory.
A Runner token cannot read the vault directly; it gets decrypted values only for runs it has claimed. The customer-run runner never writes them to disk or into JUnit reports.
What is redacted, and where it stops
Redaction is specific per artifact. So are its limits.
| Artifact | What happens | Limits |
|---|---|---|
| Recorded network data | Authorization, Cookie, Set-Cookie and headers named like a token, secret, API key or session are dropped. Password and token fields become [REDACTED], in the browser, before batching. | Matching is by name, token shape and site patterns. A credential under an unusual name can be stored; sites can add patterns. |
| Step definitions | Hold secret names, never values. | None. |
| Server logs | Request bodies and secret values are not logged. | None. |
| Playwright traces | Vault values are replaced with *** in every trace file before upload. If masking fails, the trace is not uploaded. | Values under four characters, environment variables and extracted values are not masked. |
| Screenshots | A field is drawn as dots before a secret is typed into it, and again before the failure screenshot. Sites can blank up to 20 areas by CSS selector. | A secret shown outside a field, in an area not listed, can appear. |
Because redaction has limits, pilots use staging sites, test accounts and synthetic data.
Two execution boundaries
Where a browser runs decides what it can reach.
- Hosted workers
- Sandboxed Chromium and Firefox in worker containers
- Private, loopback, link-local and cloud-metadata addresses are refused
- Navigation only to domains registered on your site
- Per-run caps on time, memory, steps and size
- Customer-run runner
- Executes inside your network, with outbound HTTPS only
- Runner tokens cannot manage members or site settings
- Cloud metadata endpoints stay blocked
- Source-available, so you can read what runs
Hosted runs are not enabled for pilot workspaces.
Questions security teams ask
Are passwords recorded?
Values typed into password fields are never recorded, and are replaced with [REDACTED] wherever they reappear in captured text. A credential typed into an ordinary field is hidden only when the field's name matches the redaction rules, so pilots use test accounts.
Where are test credentials stored?
In a write-only vault per site, encrypted with AES-256-GCM. Tests refer to them by name.
How are credentials injected during replay?
When a runner claims a run, it receives decrypted values for the names that run references and holds them in memory while the steps execute.
Which artifacts are redacted?
Recorded network data, step definitions, server logs, Playwright traces and failure screenshots, each with the limits listed in the redaction table.
Can tests run inside a private network?
Yes, with the customer-run runner on a machine inside that network. Hosted workers refuse private addresses, and hosted runs are not part of the pilot.
Does Locus hold security certifications?
Locus does not claim any certification or third-party audit. Ask at [email protected] for the details your review needs.