# AI Security Review with Jim Nittterauer

> AI is already inside your business. The question is whether you know where, what it has access to, and what happens if it gets it wrong - or gets hijacked. Most companies that come to me for an AI security review fall into one of three situations. They have adopted AI tools across the business but have no policy governing how employees use them or what data they can share. They are building or deploying an AI-powered product and need to understand the security requirements before a customer or auditor asks. Or they have heard enough about prompt injection, shadow AI, and model risk to know they should be concerned, but don't yet have the expertise in-house to assess what actually applies to them. An AI Security Review is a structured engagement tailored to where you are. We start with what you have deployed - your tools, your vendors, your workflows - map the real exposures, and leave you with a clear, prioritized action plan your team can act on immediately.

- Host: Jim Nittterauer
- Duration: 90 min
- Location: Zoom Video
- Host time zone: America/Chicago
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/getaciso/ai-security-review
- Event type id: 5009417

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5009417&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 5009417,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address)
- Optional fields: `notes` (Additional notes), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.