In the modern enterprise landscape, CI/CD pipelines are indispensable for streamlining software development and deployment. However, with sensitive data and intellectual property at stake, ensuring robust pipeline security is crucial. Appcircle offers advanced security features designed to protect your code, data, and processes at every stage.

Why CI/CD Pipeline Security Matters

CI/CD pipelines often handle sensitive data such as source code, automation scripts, and environment variables. A breach can lead to data theft, financial loss, or reputational damage, as these real-world mobile CI/CD failures show. For enterprises, maintaining a secure CI/CD environment is essential for safeguarding intellectual property and ensuring compliance with industry standards. Appcircle integrates security best practices to address these risks effectively.

How Appcircle Ensures Code Security

Appcircle prioritizes code security through its unique approach to repository access and data handling:
  • No Persistent Code Storage: Source code is fetched only during the build process and is not stored on Appcircle’s infrastructure.
  • Temporary Build Agents: Each build is run on a brand-new, isolated virtual machine that is terminated after the process, leaving no residual data.
  • Read-Only, Secure Repository Access: Appcircle uses read-only tokens to fetch repository data. Repository URLs are validated on the server, and only secure transports (HTTPS and SSH) are accepted for source checkout.
  • Encrypted Tokens and Keys: OAuth tokens and SSH keys are securely stored in a dedicated secrets manager, ensuring they remain inaccessible.
  • Strict Access Control: The Appcircle team does not have access to your source code under any circumstances.

Secure CI/CD Infrastructure with Appcircle

Appcircle’s cloud infrastructure, powered by Google Cloud Platform (GCP), offers enterprise-grade security features:
  • Isolated Virtual Machines: Each build runs on a separate virtual environment to eliminate conflicts and enhance security.
  • Ephemeral Build Agents: Virtual machines are terminated after each build, ensuring no data persists.
  • macOS Security Hardening: Runner virtual machines are hardened by disabling unused services and unnecessary telemetry endpoints, minimizing the attack surface and reducing exposure to potential vulnerabilities.
  • Authenticated Runner Communication: Every call from a runner back to the platform, such as log uploads, artifact uploads and workflow completion, is authenticated with a token unique to that runner. Runner access tokens can be revoked instantly.
  • Encrypted Communication: All communications are secured via TLS, with tokens and keys rotated regularly.
  • Secure Caching and Short-Lived Signed URLs: Cached artifacts are accessible only by the same organization. Download and upload URLs are time-limited, scoped to a single file and bound to the expected content type, and access tokens are never carried in query strings.
  • Outbound Request Protection: Webhooks, Git connection tests and chat integrations cannot reach private or internal network addresses.
  • Hardened Binary Processing: Uploaded app binaries are parsed with strict resource limits and safe XML handling.
For more details, visit Google Cloud Security.

Data Security: Protecting Secrets and Signing Identities

Appcircle provides robust security for sensitive data like signing identities, environment variables, and secrets:
  • Dedicated Secrets Management: Confidential data is encrypted and stored in a dedicated secrets manager, with keys unsealed by GCP Cloud KMS.
  • Encrypted Store Credentials: Store submission credentials, such as app-specific passwords and API key files, are stored encrypted in the secrets manager.
  • Write-Only Credentials: Once saved, Git credentials, webhook signing secrets and tester passwords are never returned in API responses.
  • Controlled Access: Users without permission cannot view or modify secrets, ensuring only authorized personnel have access.
  • Automatic Log Redaction: Secrets, tokens and one-time codes are masked across build logs, runner output and the observability pipeline, so they never reach logs or telemetry.

Identity, Authentication and Session Security

Appcircle uses Keycloak for identity and access management, with protections applied by default at sign-in and throughout each session:
  • Enterprise Identity: Sign in to the Appcircle dashboard with OpenID Connect or SAML SSO, with two-factor authentication support. Self-hosted installations also support LDAP sign-in. The Testing Distribution and Enterprise App Store portals support SSO and LDAP authentication, configured separately from the dashboard.
  • Brute-Force Protection by Default: Login lockout is on by default, with separate thresholds per account and per IP address, enforced on the server.
  • Hardened Web Sessions: The session is regenerated at sign-in, cookies are Secure-only, logout is protected against cross-site request forgery, and authenticated pages are not cached.
  • Immediate Credential Revocation: Revoking or rotating a personal access token or API key, changing a password, or reaching an API key’s expiry date ends access immediately.
  • Strict Content Security Policy: The Testing Distribution and Enterprise App Store portals run under a strict Content Security Policy that blocks dynamic code evaluation.
  • Safe Email Actions: Approve and reject links in emails require an explicit confirmation, so automated link scanners in mail systems cannot trigger them.

Advanced User Management and Logging

For enterprise teams, Appcircle provides fine-grained control and transparency:
  • Role-Based Access Control (RBAC): Assign specific roles and access levels to team members so their access is aligned with their responsibilities.
  • Custom Roles: Define granular, scope-based roles that grant permissions per action instead of per module, so each member holds only the privileges their work actually requires.
  • No Privilege Escalation Through Delegation: API keys and custom roles can never hold more permissions than their creator. Owner-level permissions stay with organization owners.
  • Role Mapping: Map user groups and role associations to Appcircle organizations and roles, simplifying user provisioning and helping maintain consistent access policies across the organization.
  • Organization Isolation: Organization ownership is verified for every resource at multiple layers of the platform, so each organization’s data stays within its own boundary.
  • Activity Logs and Reports: Monitor key actions across the platform, including workflow changes, role updates, and organization-level actions, with logs and reports that support traceability.
  • Sub-Organization Support: Manage multiple teams and projects separately through sub-organizations under a single root organization, with isolated workspaces and controlled access.
Appcircle’s user management tools ensure streamlined collaboration without compromising security.

Private Cloud and On-Premise Deployment Options

For organizations requiring complete control over their CI/CD pipeline, Appcircle offers private cloud and on-premise deployment options. These setups allow you to host the entire pipeline within your infrastructure, giving you full data sovereignty while maintaining Appcircle’s robust features.
Self-hosted installations are secure by default:
  • Trusted Proxies Only: Forwarded client headers are accepted only from proxies you configure.
  • Verified Webhooks: Signatures on incoming webhooks are always verified.
  • Controlled Internal Access: Outbound requests cannot reach internal network ranges unless you explicitly allow them.
  • Validated Email Delivery: SMTP server certificates are validated by default.
  • Protected Vault Secrets: Vault secrets are never written to container logs.

Continuous Security Validation

Appcircle holds an ISO 27001 certification and is SOC 2 Type II compliant. Beyond these audits, security is validated continuously:
  • Penetration Testing: Periodic third-party penetration tests are complemented by automated, AI-driven penetration testing.
  • Secure Code Reviews: Services are reviewed systematically, one by one, against secure coding practices.
  • Responsible Disclosure: Appcircle works with external security researchers through its public Bug Bounty Program. Vulnerabilities can be reported privately, and every valid report is prioritized by its CVSS v3.1 score.
  • Current Dependencies: The identity platform and third-party dependencies are kept on current, supported releases.
Left Icon Need documentation for your security assessment? Right Icon Contact us

Conclusion

Appcircle protects code, data and processes at every stage of the mobile CI/CD pipeline, from isolated build agents and encrypted secrets to hardened sign-in and continuous security validation. Whether you use the public cloud or host Appcircle in your own infrastructure, these protections are built into how the platform works.