SDKSecure deployment

Secure deployment

This page is a checklist for putting Syntic Code, and any program that runs it, into a team or production setting. Each step links to the page that explains it. For the design behind these controls, see Security.

1. Choose the permission baseline

Pick the mode that matches the job, and make sure no program runs in a mode it does not need.

  • Set a default mode for the team in managed settings, using Permission modes.
  • Use plan or dontAsk for read-only and report jobs.
  • Do not allow bypass on shared machines. Keep it out of the team’s managed settings and scripts, and set "permissions": {"disableBypassPermissionsMode": "disable"} in managed settings. Bypass mode then cannot be used from any source, and it is refused at the tool gate as well.

2. Write deny rules for what must never run

Deny rules always win, in every mode. Put the commands and files that must stay out of reach into a deny list in managed settings, for example production deploys, secret files and package publishing. See Permission rules and Commands that reach outside.

3. Lock the settings that matter

Settings from managed policy sit above user and project settings, and a lower layer cannot turn a locked switch back on.

  • Set managed settings with Managed settings.
  • Decide which MCP servers may be used with Managed MCP.
  • Restrict hooks to managed ones if project hooks are not trusted, with Hooks.

4. Keep the folder trust gate

Projects are untrusted until someone accepts them. Do not script around the trust question. A program that runs in an untrusted folder runs in a restricted state, and that is the intended behaviour. See Folder trust.

5. Control the network

  • Model requests can go only to the Syntic platform hosts. A project cannot change the API address.
  • Set a proxy and internal certificate authorities as described in Network configuration.
  • Choose a privacy level that matches your data rules. See Data usage.

6. Protect sign-in credentials

Credentials live in your user folder (~/.syntic, or the folder named by SYNTIC_CONFIG_DIR), readable only by your user account. Project settings cannot choose a credential. Give CI jobs their own refresh tokens, store them as secrets, and replace them when a person leaves. See Sign in.

7. Keep telemetry inside your boundary

Telemetry is off by default. If you turn it on, send it only to a collector you run, and check the privacy level that applies to the machines. See Monitor usage.

8. Review the output

The agent’s changes are only as safe as the review that follows. Run the agent’s checks, read the diff, and commit in small steps so a bad change is easy to revert. For checkpoints and their limits, see Checkpoints.

Check which features your account type and operating system support on the Feature availability page before you rely on them.