A configuration drift audit helps you find unsafe differences between PrivateBin instances before they become operational, privacy, or compliance problems. This guide provides a repeatable comparison process for deployment settings, web-server controls, upload limits, expiration behavior, storage permissions, TLS, administration, and documented environment exceptions.
Overview
Running several PrivateBin instances is common when teams separate production, testing, internal use, or regional environments. The risk is not simply that one instance is configured differently. The risk is that the difference is accidental, undocumented, or weaker than the organization’s intended baseline.
A PrivateBin configuration audit should therefore answer four questions:
- What settings and surrounding controls are deployed on every instance?
- Which differences are intentional, and where are they approved?
- Which differences create additional exposure or operational risk?
- Can the team produce evidence showing what was checked, when, and by whom?
Start by defining a baseline rather than assuming that identical files are possible or desirable. The baseline should record the expected application configuration, runtime and operating-system assumptions, reverse-proxy behavior, storage model, administrative controls, and environment-specific exceptions. Treat the baseline as a controlled security document, not as a collection of undocumented preferences.
For each instance, record its owner, hostname or internal identifier, environment, deployment method, PrivateBin release, runtime version, configuration-file location, web-server or ingress layer, storage location, and last review date. Avoid placing secrets, encryption keys, passwords, or complete sensitive configuration values in the audit record. Store evidence securely and redact values that are not needed to demonstrate compliance.
A configuration comparison is most useful when paired with an operational review. The PrivateBin deployment risk assessment template can help document business use, data sensitivity, threats, and compensating controls, while the audit evidence checklist provides a useful way to organize proof for readiness work.
Checklist by scenario
1. New instance onboarding
Before an instance accepts real data, compare it with the approved baseline and capture evidence for each control.
- Confirm the intended environment and owner are recorded.
- Verify that the deployed PrivateBin release and runtime components are supported by your organization’s maintenance process.
- Compare application configuration with the approved baseline, including expiration, upload, size, presentation, and storage-related settings.
- Check that the web server, reverse proxy, ingress, and firewall expose only the intended routes and ports.
- Confirm HTTPS behavior, certificate management, redirect handling, and security headers according to your platform standard.
- Verify that the data directory and configuration files have appropriate ownership and permissions.
- Confirm that logs do not unnecessarily capture paste contents, sensitive request data, or secrets.
- Test the documented administrative and operational access path, including who can change configuration.
2. Periodic drift review
For a monthly or quarterly review, compare current state with both the baseline and the previous approved review. A simple evidence table can use these columns: control area, expected state, observed state, instance, difference, risk, owner, due date, and evidence reference.
- Export or record configuration metadata consistently across instances.
- Compare configuration files after removing secrets and environment-specific values that cannot be shared.
- Review deployment manifests, container environment variables, infrastructure code, and startup arguments rather than checking only the application file.
- Inspect reverse-proxy and web-server changes, because an application setting can be undermined by an outer layer.
- Reconcile storage permissions, backup scope, retention behavior, and monitoring coverage.
- Close, accept, or assign every difference; do not leave unexplained deviations marked as informational.
3. Post-change validation
After an upgrade, migration, infrastructure change, or emergency fix, run a focused comparison before declaring the change complete. Confirm that the intended version and configuration were deployed to every affected instance, that permissions and TLS behavior remain correct, and that upload, expiration, and access tests produce the expected result. Use the upgrade and rollback runbook to connect configuration validation with release and recovery steps.
4. Incident or suspected exposure
Preserve the current state before making broad changes where practical. Capture configuration, relevant access-control settings, proxy rules, logs, storage permissions, and recent deployment history. Compare the affected instance with a known-good instance, but do not assume the known-good system is fully secure without checking it. If a paste may have been exposed or shared incorrectly, follow a documented response process such as the PrivateBin incident response playbook.
What to double-check
Application and data lifecycle settings
Check expiration defaults, permitted expiration choices, paste size limits, file-upload behavior, and any features that affect how long data remains available. Confirm that these settings match the data classification and stated retention policy. A short expiration setting is not a substitute for removing backups, caches, or logs that may contain related information. Review the data retention and expiration operations runbook for a broader lifecycle check.
Web-server and network controls
Inspect the full request path: DNS or load balancing, CDN if applicable, reverse proxy, web server, application runtime, and storage service. Verify that administrative or diagnostic paths are not publicly reachable, directory listing is disabled where it should be, and request limits are consistent with the application’s intended use. Test redirects and rejected methods from outside the trusted network rather than relying only on configuration review.
Storage and permissions
Record where pastes and uploaded files are stored, who can read or modify them, and how backups are protected. Compare filesystem or object-storage permissions across instances. Look for writable configuration directories, overly broad service-account access, inherited permissions, and backup locations that are more accessible than the live system. These findings often matter as much as an application configuration difference.
TLS, access, and administration
Verify certificate coverage, renewal ownership, HTTPS enforcement, and the organization’s approved TLS policy. Review how operators authenticate, whether privileged access is separated from ordinary use, and how changes are approved and recorded. If authentication or an access-control layer is used, document its scope and failure behavior; the authentication and access-control guide can support this review.
Evidence quality
Evidence should show the instance, collection date, reviewer, source, and result. Prefer configuration exports, version-control references, permission listings, test results, and change records over screenshots alone. A screenshot may demonstrate a point in time, but it is difficult to compare and may omit inherited or runtime settings.
Common mistakes
- Comparing only application files: Runtime variables, container arguments, proxy rules, and storage permissions can change the effective security posture.
- Copying production settings into every environment: Test systems may need different data, access, or network controls. Differences should be deliberate and documented, not eliminated blindly.
- Recording secrets as evidence: Prove that a secret is configured without copying its value into tickets, spreadsheets, or audit folders.
- Treating a version match as a security review: Identical releases can still run with different permissions, headers, limits, or exposure paths.
- Ignoring limits and expiration: Upload size, paste lifetime, and allowed choices affect storage use, abuse resistance, and retention expectations.
- Accepting exceptions without an owner: Every deviation needs a reason, approver, compensating control where appropriate, and review date.
- Fixing drift without preserving evidence: Capture the original finding and remediation record so the team can demonstrate what changed.
When to revisit
Run a full comparison on a regular monthly or quarterly cadence suited to the number and sensitivity of instances. Perform an additional review before seasonal planning cycles, onboarding a new environment, changing hosting or storage, modifying retention requirements, or introducing a new upload or access workflow. Recheck immediately after upgrades, rollback events, infrastructure-as-code changes, major proxy or firewall changes, and suspected exposure.
Make the review repeatable by keeping one versioned baseline, one evidence checklist, and one exception register. At the end of each cycle, prioritize findings using impact and likelihood: address public exposure, unauthorized access, unsafe storage permissions, and uncontrolled retention first; then schedule lower-impact consistency and documentation work. Assign an owner and due date to every action.
Before closing the review, complete a short validation: compare the resolved setting again, run the relevant functional and access tests, confirm monitoring is still active, and link the result to the change record. For broader operational coverage, pair this audit with the file-upload and size-limit policy guide and the monitoring and operational health checklist. This turns configuration drift detection from a one-time inspection into a practical readiness habit.