Built for CISOs reviewing CRM security

The CRM security posture a CISO can review in 20 minutes without the vendor runaround.

CRM evaluations stall at security review for 60 to 180 days with checklist back-and-forth, SOC 2 renewal uncertainty, scope ambiguity on AI retrieval, and vendor claims that do not survive a careful read. Strkr publishes the posture plainly: HIPAA BAA on request, SOC 2 Type II in progress with a 2026-Q4 target, SAML and OIDC SSO through Clerk on the Scale tier, TOTP MFA across tiers, verified domains, scoped AI retrieval, and a full audit log.

What this audience is actually dealing with

The pains that bring buyers here.

CRM security reviews stall at the same four or five questions every time: what is the SOC 2 status actually, does the AI retrieve cross-tenant data, is HIPAA real or marketing copy, does SSO cost extra, what does the audit log actually capture. Vendors answer these with ambiguous checklists, roadmap language, and promises that depend on a sales call. The pain points below are what Strkr onboarding hears on every intake call with a CISO reviewing CRM for a mid-market or enterprise deployment.

SOC 2 renewal uncertainty

The report expires in six weeks and nobody says it.

A vendor pointing at a SOC 2 Type II report that expires in six weeks and has no documented renewal plan is not actually SOC 2 compliant on the day the contract starts. Strkr states the SOC 2 posture plainly: SOC 2 Type II is in progress with a 2026-Q4 target completion. For CISOs evaluating pre-completion the readiness report is available on request and the audit firm engagement is confirmable in writing.

HIPAA ambiguity

The marketing page says HIPAA, the BAA does not exist.

A vendor marketing page that says HIPAA compliant without a BAA offer is marketing. HIPAA compliance means a Business Associate Agreement signed, PHI handling scoped, breach notification processes documented, and the vendor accepting liability. Strkr offers a BAA on request across all tiers, scopes PHI handling in writing, and documents breach notification processes. Not a tier gate.

SSO behind an enterprise paywall

The SAML pricing uplift is 300 percent.

Most SaaS vendors gate SAML and OIDC SSO at the enterprise tier with a 200 to 400 percent uplift over the standard tier. For a 40-seat deployment this adds $42,000 to $140,000 per year for a security control that should be table stakes. Strkr ships SAML and OIDC SSO through Clerk at the Scale tier ($119 per seat) with no uplift beyond the tier price and verified domains included.

AI retrieval scope

The AI pulls cross-tenant data without the admin knowing.

A CRM with AI drafting that retrieves across tenants, across accounts, or across matters without scope control is a privilege and privacy violation waiting to happen. Strkr AI runs with retrieval scope strictly configured per prompt (default scope is the current record and its direct relationships) and the admin tunes scope per prompt in the admin console. Cross-tenant retrieval is architecturally disabled.

Audit log completeness

The log captures writes, misses reads, loses retention.

A CRM audit log that captures writes but not reads cannot answer the common CISO question of who viewed what, when. A log with a 30-day retention default cannot answer the common forensic question of what happened 60 days ago. Strkr audit log records every record read, every record write, every email sent, every AI prompt invoked, with 90-day default retention tunable per tenant up to the regulatory maximum.

Vendor claims that do not survive a read

The marketing page says one thing, the DPA says another.

Vendor marketing frequently claims security posture that the Data Processing Addendum contradicts. The CISO review surfaces this on the third pass, which wastes six weeks of evaluation. Strkr publishes the posture plainly on the trust page, the DPA matches, the subprocessor list is public, and the security team responds to vendor assessment questionnaires within three business days.

The CISO review surfaces

What Strkr publishes for security review on day one.

A CISO reviewing a CRM wants six things in writing: identity and access management posture, data protection posture, audit and logging posture, compliance posture, incident response posture, and subprocessor transparency. Strkr publishes each on the trust page with the specifics printed, not the marketing framing. The CISO review runs in 20 to 40 minutes instead of 60 to 180 days.

Identity and access

SAML, OIDC, SCIM, MFA, verified domains.

SAML and OIDC SSO through Clerk on the Scale tier. SCIM provisioning for user lifecycle automation. TOTP and text-based MFA across all tiers. Verified domains at Scale for tenant protection. Session policy configurable per tenant with inactivity timeout and absolute session cap.

Data protection

Encryption at rest and in transit with KMS.

AES-256 encryption at rest with AWS KMS. TLS 1.3 in transit. Per-tenant encryption keys available on Scale. Secrets handled through AWS Secrets Manager with per-tenant OAuth tokens for integrated services. Backup posture documented with recovery point objective of under four hours.

Audit and logging

Read, write, email, AI, with 90-day retention.

Audit log captures every record read, every record write, every outbound email, every AI prompt invoked, with the actor, timestamp, source IP, and session identifier. 90-day retention default tunable per tenant up to seven years for regulatory requirements. Log export through API for SIEM integration.

Compliance

HIPAA BAA, SOC 2 Type II in progress, GDPR, CCPA.

HIPAA compliant with BAA available on request across all tiers. SOC 2 Type II in progress with 2026-Q4 target. GDPR and CCPA posture live today with data subject access request workflow, right-to-delete automation, and consent capture. Trust page carries current status with the audit firm and target date printed.

Incident response

Documented runbook with notification SLAs.

Incident response runbook with severity classification, notification SLAs (24 hours for confirmed breach, 72 hours for suspected), and customer-communication templates. Post-incident report with root cause, scope, impact, and remediation within 14 days of resolution. Public status page at status.strkr.io with real-time component health.

Subprocessor transparency

Public list with change notification.

Subprocessor list published with the trust page, change notification 30 days before new subprocessor onboarding, right of objection for customers under GDPR. Current list includes AWS (hosting), Clerk (identity), Stripe (billing), and the AI model provider (model routing).

How Strkr handles AI retrieval scope

The AI control surface a CISO can tune.

The biggest unanswered question in CRM AI security is retrieval scope. A CRM AI that retrieves cross-tenant, cross-account, or cross-matter data on draft generation is a privilege and privacy violation vector. Strkr publishes the retrieval architecture plainly and the admin tunes scope per prompt without a support ticket.

Default retrieval scope

The current record and direct relationships.

Default scope for AI drafting is the current record (deal, account, contact, matter) and its direct relationships (owner, team, attachments). The AI does not retrieve across tenants, across accounts without explicit opt-in, or across matters without admin configuration. The default is the safe default.

Scope tunability

Per-prompt configuration in the admin console.

The admin tunes retrieval scope per prompt in the admin console. The configuration options are documented: current record only, current record plus relationships, account-wide, workspace-wide, team-wide. The admin sees the scope on every AI prompt invocation in the audit log.

Cross-tenant isolation

Architecturally disabled.

Cross-tenant retrieval is architecturally disabled, not just policy-disabled. The data path from AI prompt to data source enforces tenant isolation at the storage layer, not just the application layer. A compromised prompt cannot retrieve another tenant data.

Model routing transparency

The model that handled each prompt is in the log.

The audit log records the model that handled each AI prompt (default is the lower-latency model for simple drafts, the higher-reasoning model for complex analysis). The admin can lock model routing per prompt or per workspace. The CISO can verify no prompt was routed to a model outside the approved vendor list.

Data residency for AI calls

US regions by default with regional override.

AI model calls route to US regions by default. The admin can configure regional routing per workspace for EU residency requirements, with the model vendor and region printed in the audit log. The DPA documents the data residency commitment per region.

Prompt and completion retention

Not retained by the model vendor.

AI prompts and completions are not retained by the model vendor beyond the request lifecycle for training or evaluation purposes. The commitment is in the DPA with the model vendor and documented in the Strkr subprocessor list. The audit log retains the prompt metadata (model, timestamp, actor, retrieval scope) with 90-day default retention.

The CISO review pricing math

What Strkr costs with the full security posture included.

The pricing math below is for a 40-seat deployment with SSO, verified domains, HIPAA BAA, and extended audit retention. The numbers come from Strkr onboarding intake calls with real CISOs in 2026. The invoice math holds because Strkr prices flat per seat with the security posture included at the Scale tier, no separate security module charge.

Strkr Scale

$119 per seat per month, 40 seats.

Forty seats on Scale run $4,760 per month. Scale includes SAML and OIDC SSO through Clerk, verified domain capture, HIPAA BAA on request, extended audit retention (configurable up to seven years), and the full compliance posture. Total annual spend for a 40-seat Scale deployment is $57,120 with the full security feature set.

Strkr Pro plus BAA

$59 per seat with HIPAA BAA on request.

The HIPAA BAA is available on request on any tier, not just Scale. For CISOs comfortable with TOTP MFA without SAML SSO, Pro at $59 per seat covers the compliance posture at $2,360 per month for 40 seats. SOC 2 Type II in progress applies at every tier equally.

Audit retention

Tunable up to seven years.

The audit log retention default is 90 days on every tier. Retention can be tuned up to the regulatory maximum (seven years for HIPAA, varying by state for other regulations). Extended retention is included in all tiers at no additional charge.

Salesforce Enterprise

Floor $150 per seat plus Shield at $25.

Salesforce Enterprise starts at $150 per seat. Salesforce Shield (field encryption, audit log retention extended, event monitoring) adds $25 to $75 per seat. For 40 seats the monthly invoice lands around $7,000 to $9,000 before the Platform Encryption add-on and the implementation retainer.

HubSpot Enterprise

Floor $150 per seat with security tier gating.

HubSpot Enterprise starts at $150 per seat. SSO lands at the Enterprise tier. Field-level permissions require Operations Hub Enterprise. For 40 seats the monthly invoice lands around $6,000 to $8,500 before credit overages on marketing contacts and Breeze AI.

The 12-month total cost

What a 40-seat deployment actually spends.

Across 12 months a 40-seat Strkr Scale deployment spends $57,120 with the full security posture. The same deployment on Salesforce Enterprise plus Shield typically spends $90,000 to $130,000 before implementation. On HubSpot Enterprise the number lands at $72,000 to $110,000 before marketing-contact credit burn. The compound effect is real, and the full security feature set is included.

Head-to-head

Strkr vs typical CRM security postures.

The comparison below is Strkr Scale versus the typical enterprise CRM alternatives on the security posture that matters for CISO review.

Feature Strkr Salesforce or HubSpot Enterprise
SAML and OIDC SSO Scale tier $119 per seat. Enterprise tier $150+ per seat.
HIPAA BAA availability On request across tiers. Enterprise-only add-on.
SOC 2 Type II In progress 2026-Q4 target. Available with current scope.
AI retrieval scope control Per-prompt in admin console. Opaque or no control.
Audit log read capture Default on across tiers. Shield add-on or Enterprise tier.
Audit log retention default 90 days tunable to seven years. 30 to 90 days typical.
Subprocessor list public Trust page with change notification. DPA-only typical.
Verified domains Scale tier. Enterprise tier.
Session policy configuration Per tenant across tiers. Enterprise or Shield.
Monthly cost for 40 seats $4,760 Scale with full posture. $7,000 to $9,000 Enterprise plus Shield.
How teams use Strkr

Five CISO review playbooks.

The playbooks below are patterns Strkr security team sees on CISO review across sizes and verticals. Each pattern is a real customer motion from the 2026 cohort.

Pattern A

The 20-seat healthcare SMB deployment.

A 20-seat healthcare SaaS SMB required HIPAA BAA, SAML SSO, and 180-day audit retention. The CISO reviewed Strkr Scale, confirmed the BAA language, verified SSO through Clerk, and configured the 180-day retention in the admin console. The security review completed in 24 business days versus the 90-day baseline. Monthly spend lands at $2,380 across 20 seats on Scale.

Pattern B

The 60-seat financial services mid-market deployment.

A 60-seat financial services firm required SAML SSO, verified domains, SIEM log export, and model routing transparency. The CISO reviewed Strkr Scale, configured SSO through Clerk, enabled verified domains, set audit log export to the firm Splunk instance via REST API, and locked model routing to the US-East region. Review completed in 18 business days. Monthly spend lands at $7,140.

Pattern C

The 180-seat software vendor enterprise deployment.

A 180-seat enterprise software vendor required SAML, SCIM provisioning, 365-day audit retention, DPA with specific subprocessor language, and penetration test report access. The CISO reviewed Strkr Scale, provisioned SCIM, extended audit retention, negotiated the DPA with the Strkr legal team, and received the most recent penetration test summary under NDA. Review completed in 32 business days. Monthly spend lands at $21,420.

Pattern D

The eight-seat regulated-industry startup.

An eight-seat Series A fintech startup needed HIPAA BAA for a potential healthcare segment customer and SAML SSO for a potential enterprise customer. The CISO wanted the posture ready before the first enterprise security review landed. Strkr Scale shipped the full posture in week one of the deployment, which closed two enterprise deals in the next quarter without delayed security reviews.

Pattern E

The 40-seat multi-regional EU deployment.

A 40-seat software company with EU and US operations needed GDPR data residency per workspace, SCIM provisioning from Okta, and the audit log export to Datadog. Strkr Scale configured EU model routing for the EU workspace, provisioned SCIM, and set audit log export through API. Review completed in 22 business days. Monthly spend lands at $4,760 plus the AI add-on.

Review the CRM security posture in 20 minutes, not 20 weeks.

Book a 30 minute call with the Strkr security team. We will walk through the trust page, the AI retrieval scope controls, the audit log, the DPA, and the BAA with your specific review checklist.

Common questions

What buyers in this bucket ask most.

Can a CISO complete the Strkr security review in under 30 business days?

Yes for most reviews. The Strkr trust page publishes the full posture (identity, data protection, audit, compliance, incident response, subprocessors) with the specifics printed. The security team responds to vendor assessment questionnaires within three business days. The DPA and BAA templates are available on request within 24 hours. For reviews requiring specific controls (SIEM integration, custom retention, regional routing) the configuration completes in week one of the deployment. The average review closes in 18 to 32 business days versus the 60 to 180 industry baseline.

What is the actual SOC 2 status today?

SOC 2 Type II is in progress with a 2026-Q4 target completion. The audit firm engagement is confirmable in writing. The readiness report is available on request. For CISOs requiring Type II report delivery before contract start, the Strkr sales team provides the target date with the audit firm named, and the contract can include a SOC 2 completion milestone clause. The posture is honest: the report is not available today, the audit is active, the target is public.

How does Strkr actually handle HIPAA?

Strkr offers a Business Associate Agreement on request across all tiers. The BAA documents PHI handling scope, breach notification processes, vendor accountability, and subprocessor flow-down. The engineering posture includes encryption at rest with AES-256, TLS 1.3 in transit, access logging, and workforce training on HIPAA. The BAA is not a tier gate: a Starter deployment at $29 per seat can execute a BAA and handle PHI with the same engineering posture as a Scale deployment.

Does the AI retrieve across tenants or across unrelated accounts?

No. Cross-tenant retrieval is architecturally disabled at the storage layer, not just policy-disabled. The default retrieval scope for AI drafting is the current record and its direct relationships. Cross-account retrieval within the same tenant requires explicit admin configuration per prompt in the admin console. The audit log records the retrieval scope on every AI prompt invocation so the CISO can verify the scope matches the policy on an ongoing basis.

What does the audit log capture and how long is it retained?

The audit log records every record read, every record write, every outbound email, every AI prompt invoked, with the actor, timestamp, source IP, and session identifier. Default retention is 90 days. Retention can be tuned per tenant up to the regulatory maximum (seven years for HIPAA, varying by state for other regulations) at no additional charge. Audit log export through the REST API supports SIEM integration (Splunk, Datadog, Elastic, Sumo Logic).

How does Strkr handle incident response and breach notification?

Incident response runbook with severity classification, notification SLAs (24 hours for confirmed breach, 72 hours for suspected), and customer-communication templates. Post-incident report with root cause, scope, impact, and remediation within 14 days of resolution. Public status page at status.strkr.io with real-time component health. The CISO receives direct notification per the DPA with the contact and escalation path documented in advance.

How does Strkr pricing stay flat with the full security posture included?

Scale tier at $119 per seat per month includes SAML and OIDC SSO through Clerk, verified domains, extended audit retention, SCIM provisioning, and the full compliance posture. There is no separate security module charge, no Shield-equivalent add-on, and no implementation partner retainer. A 40-seat deployment on Scale lands at $57,120 per year with every security feature included, versus $84,000 to $130,000 on Salesforce Enterprise plus Shield.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.