Trust & Security

Any vendor with access to your systems falls inside the scope of your security audits. Albacore is built to be a simple check in that review, not a remediation project.

We work under least-privilege access, keep your production and customer data inside your environment, and leave every change traceable in your own version history. Our practices are designed to line up with the controls your auditors already test.

Environment & Data Isolation

• Production and Customer Data Stays Put: Albacore does not host client applications or move client production or customer data onto Albacore-owned hardware or cloud storage.
• Source Code: To do the work, we may clone source repositories to Albacore workstations. Those devices are full-disk encrypted, MDM-managed, and require a hardware security key, and we remove client source code from them at the end of an engagement.
• Native Operations: Infrastructure provisioning and configuration happen inside client-controlled identity providers and cloud accounts, using credentials you issue and can revoke at any time.

Identity & Access

• Phishing-Resistant MFA: Multi-factor authentication is required on every account we use to reach client systems, our communication channels, and our own infrastructure. Where a service supports it, we use phishing-resistant methods such as hardware security keys (YubiKey) and passkeys.
• Least Privilege: We request scoped, time-bound access limited to the systems an active engagement requires, with no standing access beyond it.
• Offboarding: At the end of an engagement, or on request, we stop using and return any access you granted, remove client source code from our devices, and confirm the teardown in writing. We retain a copy of that confirmation for our own records and prompt you to revoke or rotate the credentials you issued.

Tooling & AI Assistance

• No Unapproved Services: We do not introduce new services or dependencies into your stack without sign-off.
• Controlled AI Use: We use AI coding assistants only on business-tier accounts that do not train on or retain our inputs beyond their operational requirements. We never submit client source code to consumer AI tools or any service that trains on it.

Auditability & Accountability

• Traceable to a Named Individual: Because we work through credentials you issue, every change we make is attributable to a named person in your own version history, identity logs, and cloud audit trails.
• You Retain Visibility: You keep full, native visibility into what we do, when, and where, with no reliance on Albacore to produce its own records.

Endpoint Integrity

• Encrypted, Locked Devices: All Albacore workstations use full-disk encryption (such as FileVault) and require a hardware security key (YubiKey) to log in.
• Per-Client Separation: Client credentials, SSH keys, and configurations are isolated per client. Nothing is shared or reused across engagements.

Incident Response

• Prompt Notification: If we identify a security event affecting client systems or data, we notify the affected client promptly and support investigation and remediation. Notification timelines are defined in each engagement agreement.