Security reviewers
Security overview
This page is written for the person who has to approve BucketDesk. It summarises how access works and links to the two pages that hold the detail: Security and What BucketDesk can do in your AWS account, which lists every IAM action.
How access works#
Your files stay in your own Amazon S3 buckets. BucketDesk reaches them through an IAM role that you create in your account from a CloudFormation template. No access keys are exchanged.
| Control | What it means |
|---|---|
| A role in your account | You create it by submitting a CloudFormation stack after reviewing every resource and permission. You own it, and CloudTrail records each session that uses it. |
| Your own external ID | Each setup gets a random 64-character external ID. The role trusts one BucketDesk role, and only when the request carries that ID. |
| Short-lived credentials | BucketDesk works with temporary credentials that expire after 15 minutes. BucketDesk Sync on a laptop receives one-hour keys. |
| Buckets you choose | The file role can reach every bucket in the AWS account, so one setup covers buckets you add later. Your admins choose which buckets join the workspace, and BucketDesk’s code keeps every file request inside those. |
| Every capability from the start | The roles carry every capability, so a new feature never needs another AWS step. Your plan decides which ones the workspace can use, and member roles decide who can upload, delete or share. |
| You change the role | When a BucketDesk release needs different permissions, the app shows an update and opens a CloudFormation change that you review and submit. The stack changes only when you submit it. |
To end access, delete the stack. The role goes with it and BucketDesk’s next request is refused.
Threats and what limits them#
| Threat | What limits it |
|---|---|
| Long-lived AWS keys leak | There are none to leak. BucketDesk holds only temporary credentials from the role, and they expire within 15 minutes. |
| Someone else points BucketDesk at your role | The role answers only to requests carrying your connection’s external ID. BucketDesk also refuses connections to roles in its own AWS accounts. |
| BucketDesk reaches more than you intended | The IAM policy names one bucket and folder. The few permissions AWS cannot scope to a folder are listed, with the reason for each, on the AWS access page. |
| Files are changed or deleted by mistake | Member roles decide who can upload, delete or share, and your plan decides which of those features the workspace uses. With the recycle bin, deleted files wait 30 days inside your bucket. |
| A member’s password is stolen | Owners and admins must set up two-factor authentication before managing connections, members, tokens or tools. Changing a password signs out other sessions, API tokens and AI connections. |
| A teammate leaves | Removing a member immediately revokes their share links, API tokens and AI assistant connections, and signs their devices out on the next request. |
| A share link is forwarded | Share links expire and can be revoked, and every open is recorded in the activity log. |
Identity and sign-in#
- Members sign in with an email and password or a passkey, and can add an authenticator app as a second step.
- Workspace owners and admins must set up two-factor authentication before managing connections, members, tokens or tools. New accounts get 14 days to set it up.
- BucketDesk Sync and the iPhone app sign in through the browser with OAuth and PKCE. Access tokens last one hour and refresh tokens 30 days, kept in the device’s keychain.
- API tokens always expire, within a year at most. AI assistant access tokens last one hour.
- Workspace roles control who can view, operate, share and administer. Viewers cannot create share links or upload. The admin guide lists each role.
- Single sign-on, with OpenID Connect or SAML 2.0, comes with the self-hosted edition. Automatic user provisioning is arranged by quote; contact us.
Where file contents travel#
| What | Path |
|---|---|
| Downloads, images, video and audio | BucketDesk signs a short-lived S3 link and your browser fetches the file directly from your bucket. |
| Uploads | Your browser sends the file to your bucket in parts, each over its own signed link. |
| Text, PDF, HEIC photos and thumbnails | Streamed through the BucketDesk servers in memory for the length of the request, then discarded. |
| Word, Excel and PowerPoint | The BucketDesk document server fetches the file with a short-lived link and holds it while the document is open. Edits are saved back to your bucket. |
| Document chat | The file passes through the BucketDesk servers to Amazon Bedrock in your own AWS account. Chats you keep are stored encrypted for 30 days after their last use. |
| Archive extraction and Convert | Run on AWS Batch in your account, reading and writing your bucket there. BucketDesk receives a summary of each job: counts and settings, never file names or contents. |
BucketDesk does not index your bucket and its servers do not keep copies of your files.
What BucketDesk keeps#
File contents stay in your bucket. BucketDesk keeps records about them. The main ones are below; the AWS access page has the full table.
| Record | Contains | Kept for |
|---|---|---|
| Connection settings | Account ID, region, bucket and folder. Role ARNs and the external ID are erased the moment you disconnect. | 30 days after you disconnect |
| Activity log | Who viewed, shared, moved or deleted which file path | 13 months |
| Shares | File paths and recipient email | 90 days after expiry |
| Kept chats | Questions, answers and cited passages | 30 days after last use |
| Jobs and notifications | File paths for uploads, restores, moves and deletes; file names in alerts | 90 days after they end |
| Database backups | Everything above, as of each hourly copy | 35 days, locked against early deletion |
Encryption#
- All traffic uses TLS 1.2 or 1.3; older protocols are refused.
- BucketDesk’s database and backups are encrypted at rest.
- File names in notifications and activity details, connection secrets and document chats are encrypted again by the application.
- Sign-in, share and API tokens are stored only as one-way hashes.
- Buckets encrypted with a customer-managed KMS key work when you name the key in the stack. The role can then use that one key, only through S3 in your region.
Infrastructure and operations#
- The hosted service runs on AWS in the United States (us-east-1).
- Web traffic arrives through Amazon CloudFront with AWS WAF, and the server refuses requests that do not come through it. The database is not reachable from the internet.
- The database is copied every hour to a separate AWS account, where each copy is kept 35 days and cannot be deleted early. The server is snapshotted daily.
- Every change goes through code review, known high or critical vulnerabilities block a push, and the running containers are scanned every day. See how each layer is watched.
- Application logs record request paths without query strings, so share tokens and search terms are not logged.
Audit#
There are two records, and they answer different questions.
- The BucketDesk activity log records which member viewed, shared, moved or deleted which file, and administrative changes. It is kept for 13 months.
- AWS CloudTrail in your account records each session that uses the role and each call made under it. It is yours and BucketDesk cannot change it.
Shared responsibility#
| You | BucketDesk |
|---|---|
| Which bucket and folder each connection reaches | Keeping every request inside that bucket and folder |
| Which capabilities are switched on in the stack | Asking only for the permissions each capability needs |
| Who is invited, with which role, and removing them when they leave | Enforcing roles, two-factor rules and token expiry |
| Your bucket’s own settings: versioning, encryption, bucket policy, lifecycle | Patching, monitoring and backing up the hosted service |
| Deleting the stack when you stop using BucketDesk | Erasing role details at once when you disconnect |
The self-hosted edition#
If the hosted service cannot be approved, the self-hosted edition runs the whole app in your AWS account or on your own servers, reached only from your network. The server sends nothing to BucketDesk: licence keys are validated locally with a public key. See the install guide.
Compliance and reporting#
BucketDesk follows written security procedures for access reviews, change management, incident response, backups and vendor review. It does not yet hold a SOC 2 report or other third-party certification. We can answer your questionnaire and share more detail under NDA.
To report a vulnerability, email info@bucketdesk.com with “Security report” in the subject line.
Something wrong or missing on this page? Email info@bucketdesk.com. Last updated November 12, 2026.