# Security Certificate

> Security and compliance section printed like a banknote. Each certification is a certificate with its own guilloché rosette and ink that engraves itself when chosen. A UV lamp follows the pointer to reveal fibres and a hidden verification line, the hologram seal catches the light, and pending audits are stamped. Plus a controls ledger and a report request form.

- Slug: `security-certificate`
- Category: [Features](https://www.assembli.design/category/features.md)
- Type: block
- Tags: security, compliance, trust, soc-2, certificates, enterprise, guilloche, hologram, form
- npm dependencies: motion, lucide-react
- shadcn/ui dependencies: none
- Live preview: https://www.assembli.design/preview/security-certificate
- Page: https://www.assembli.design/components/security-certificate

![Security Certificate preview](https://www.assembli.design/thumbnails/security-certificate-light.png)

## Props

Other props pass through to the root element.

| Prop | Type | Default | Description |
| --- | --- | --- | --- |
| `eyebrow` | `React.ReactNode` | `"Security & compliance"` |  |
| `title` | `React.ReactNode` | `"Security you can check for yourself"` |  |
| `intro` | `React.ReactNode` | `"Independent auditors test our controls every year. Hold a …` |  |
| `issuer` | `string` |  | Your company, printed as "Issued to …" and in the microtext border. |
| `certifications` | `SecurityCertification[]` | `DEFAULT_CERTIFICATIONS` |  |
| `defaultCertification` | `string` |  |  |
| `controls` | `SecurityControl[]` | `DEFAULT_CONTROLS` |  |
| `controlsTitle` | `React.ReactNode` | `"Built into every plan"` |  |
| `note` | `React.ReactNode` |  | A footnote beside the links, e.g. when controls were last reviewed. |
| `links` | `{ label: string; href: string }[]` |  |  |
| `onRequestReport` | `(request: { certification: SecurityCertification; email: string }) => void \| Pr…` |  | Called with the email from the request form. Return a promise to show a pending state. |

## Install

One-time setup (needs a subscription):

1. Add the registry to the project's `components.json`: `{"@assembli":{"url":"https://www.assembli.design/r/{name}.json","headers":{"Authorization":"Bearer ${ASSEMBLI_API_KEY}"}}}` (merge into `"registries"`).
2. Put an API key from https://www.assembli.design/account in `.env.local` as `ASSEMBLI_API_KEY=asm_…`.

Then install with the shadcn CLI (writes `components/security-certificate/security-certificate.tsx` and installs dependencies):

```bash
npx shadcn@latest add @assembli/security-certificate
```

Registry item JSON: https://www.assembli.design/r/security-certificate.json (send `Authorization: Bearer <api key>`)

## Code

> Component source needs an Assembli subscription ($12/month or $96/year) and an API key sent as `Authorization: Bearer <key>`. To get one without copying anything, POST https://www.assembli.design/api/agent/login (or call the MCP tool connect_account), show the user the link it returns, and poll https://www.assembli.design/api/agent/token for the key. Or subscribe at https://www.assembli.design/pricing and create a key at https://www.assembli.design/account.