Use a dedicated temporary account where the platform supports it. Grant only the privileges and systems needed for the authorized task.
Operational safeguards · Reviewed September 6, 2026
Security is part of the operating model.
Practical expectations for privileged access, production changes, migration data, open-source software, and responsible vulnerability reporting.
Access first
Reduce the risk created by access itself.
Production support begins with knowing who can reach what, for how long, and what evidence should remain after the work is complete.
Share secrets through an agreed secure channel, keep MFA enabled, and revoke temporary accounts or rotate shared credentials afterward.
Identify dependencies, preserve useful evidence, and confirm a recovery path or relevant backup before material changes when conditions allow.
Migration safeguards
Short-lived data. Explicit boundaries. Verified transport.
The hosted IMAP migration tool uses an access code, validates form sessions, restricts targets to public hostnames, and uses encrypted IMAP connections with peer-certificate verification.
Temporary job data is stored outside the public web root.
Credential files are restricted to the service account and deleted when the migration process exits.
Private operational job logs expire after 24 hours.
Do not submit credentials unless you are authorized to access both mailboxes.
Open source and reporting
Make the safe path clear to the next operator.
Public repositories provide their source, licensing, documentation, and available security-reporting instructions on GitHub. Review scripts before privileged execution and test changes on non-critical systems.
Do not publish an unconfirmed vulnerability, customer information, credential, or exploit detail in a public issue. Send a concise private report to help@cyberducttape.com with the affected URL or project, impact, reproduction steps, and a safe way to follow up.