Langford Ledger

Holding client data

Needs setup. Still a 0.x release; the research notes its setup is changing between versions.

What “Tested” means

Started from the project's published images and signed in as a new admin; the page showed "Homepage". Testing shows the app starts and signs in. It is not a security audit.

I run a:

Rules this helps you meet: GLBA Safeguards Rule — The safeguards apply once we host it

You hold customer information, so you need a written information security program (WISP), and every vendor that touches the data belongs in it. This hosting covers on our side several elements of the Safeguards Rule under the Gramm-Leach-Bliley Act (GLBA): encryption, logging and monitoring, access limits and change control. For advisers and broker-dealers it helps you meet the safeguarding parts of SEC Regulation S-P. Below are vendor due-diligence questions answered for Langford Ledger · Standard.

What your examiner or auditor will ask

Is customer information encrypted at rest and in transit?

Yes. Storage encryption is always on, and every connection uses TLS 1.2 or later.

BuiltEvidence: the checks below · our control listMaps to: FTC Safeguards Rule under GLBA (16 CFR 314.4(c)(3))

Is multi-factor authentication (MFA) required for anyone who accesses customer information?

Not by default. Turn on this app's own two-step sign-in if it has one. Our platform-wide sign-in with authenticator codes is designed but not built yet.

Designed, not builtEvidence: the checks below · our control list

Do you log and monitor user activity?

Our hosting logs every database and storage access to a separate archive kept 6 years. A per-user activity screen inside the app depends on the app; our built-in one is designed, not built. Each customer's setup is also assessed continuously against the hosting rules.

BuiltDesigned, not builtEvidence: the checks below · our control listMaps to: FTC Safeguards Rule under GLBA (16 CFR 314.4(c)(8), 314.4(d)(2))

Is access limited to authorized users and systems?

Our side: the app's identity can reach only its own database and storage, and nothing is reachable from the internet except the app. Inside the app, row-level limits are designed, not built; use the app's roles.

BuiltDesigned, not builtEvidence: the checks below · our control listMaps to: FTC Safeguards Rule under GLBA (16 CFR 314.4(c)(1))

How are changes to the system managed?

Every change is code, pinned to an exact image, and recorded with who made it.

BuiltEvidence: the checks below · our control listMaps to: FTC Safeguards Rule under GLBA (16 CFR 314.4(c)(7))

Can customer information be securely disposed of when you leave?

The whole setup can be destroyed on request. Export and delete of single records inside the app is designed, not built.

Designed, not builtEvidence: the checks below · our control list

Do your records meet broker-dealer write-once record-keeping?

Not yet. Our audit archive is write-once (WORM), but its lock is not engaged yet, so it does not yet meet broker-dealer record-keeping rules. It also holds audit logs, not your business records.

Not yetEvidence: the checks below · our control list

What's still on you

Your written information security program (WISP), the person in charge of it, and your risk assessment. Our answers go in it; they are not it.
MFA on the rest of your systems: email, custodian and CRM logins.
Privacy notices and incident response for your customers.
Vendor oversight: keep this page and the check results on file, and re-check them each year.

The 12 checks we run

These run on your setup when we launch it.

Customer information is kept on a private database no one on the internet can reach runs when we set it up
Customer documents are kept in private storage with no internet address runs when we set it up
No shared password opens the file storage; only this app's own identity can get in runs when we set it up
Customer information is encrypted whenever it moves runs when we set it up
The app only answers over encrypted (https) connections runs when we set it up
Every change to customer information is logged and kept for review runs when we set it up
Customer information can be restored to any point in the last 35 days runs when we set it up
Settings that would weaken any of this are blocked automatically runs when we set it up
Your setup is reviewed continuously against the security rules for your kind of data runs when we set it up
The app is up at its own secure address runs when we set it up
Nothing in the app opens without signing in first runs when we set it up
A stranger who guesses a file's address gets “access denied” runs when we set it up

Tested is not an audit. We check our hosting and test that the app starts and signs in; meeting these rules is still your program's job.

Langford test reportOct 21, 2026

Started from the project's published images and signed in as a new admin; the page showed "Homepage".

The result file is under Technical details.

Customer reviews appear here once offices are using it.

Built on: Bigcapital (open source)
Licence: AGPL-3.0 | AGPL-3.0
Database: MySQL + ClickHouse? (compose shows clickhouse, garage S3) [compose]
Docker: yes [compose]
Peak memory in our test: 471.3 MB
Images: nginx:1, bigcapitalhq/webapp:latest, bigcapitalhq/server:latest, mariadb:10.11, redis:7-alpine, gotenberg/gotenberg:7
Source: https://github.com/bigcapitalhq/bigcapital
Website: https://bigcapital.app
Tested on: Oct 21, 2026
Test result file: runs/catalog-boot-2026-10-20/bigcapital/result.json

Hosting checks (for your IT person)

From our last MySQL hosting check run: runs/mysql-test-2026-10-21/verify.txt. 12 of 12 passed. Control ids are defined in docs/CONTROLS.md.

Result	Check	What was checked
Pass	NET-PRIVATE	mysql public network: Disabled
Pass	NET-PRIVATE	storage public network: Disabled
Pass	IAM-WORKLOAD	storage shared key: false
Pass	ENC-TRANSIT	mysql require_secure_transport: ON
Pass	ENC-TRANSIT	container app allowInsecure: false
Pass	AUDIT-LOG	mysql audit_log_enabled: ON
Pass	BACKUP	mysql PITR days: 35
Pass	GUARDRAILS	deny assignments on rg: 8
Pass	POSTURE	audit initiatives on rg: 2
Pass	ENC-TRANSIT	GET <your app address> 200
Pass	AUTH-UNIQUE	/books without a session: 302
Pass	NET-PRIVATE	anonymous blob read from the internet: 403

Screenshots

About this app

What it replaces

Information

Other editions of Langford Ledger