# Replace Cloudflare zone security

> `GET`: the zone's security defaults, read live from Cloudflare and graded by the shared Cloudflare Checkup checks, falling back per setting to the latest che...

Source: https://docs.vigilbase.com/one/api/reference/services/put-services-cloudflare-zones-zone-id-security

`PUT https://one.vigilbase.com/api/services/cloudflare/zones/{zoneId}/security`

`GET`: the zone's security defaults, read live from Cloudflare and graded by the shared Cloudflare Checkup checks, falling back per setting to the latest checkup. The eight pre-2026-10 top-level fields (`ssl`, `waf`, ...) stay, with the same values as `settings`. `PUT` answers with the same view, read again after the write.

> Needs a recent sign-in: renewing a token doesn't count, and MCP sessions and API keys are always refused. See [changes that need a recent sign-in](https://docs.vigilbase.com/one/api#changes-that-need-a-recent-sign-in).

## Authorizations

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person.

## Path parameters

- `zoneId` (string, required)

## Body (application/json)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`. API keys can't call this.
curl --request PUT \
  --url 'https://one.vigilbase.com/api/services/cloudflare/zones/{zoneId}/security' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'
```