AI

4 key considerations for scoping your ISO 42001 audit

Avoid the pain of an unclear AI governance project.

Dec 10 •

2nd party contractual risk

How detailed usage restrictions on AI content help no one.

Dec 9 •

How StackAware describes AI training

Managing risk through clear language.

Dec 4 •

Getting patients to better doctors, faster with generative AI

Case study: managing risk for Embold Health's EVA product.

Nov 15 •

ISO 42001 vs. HITRUST AI security certification

The former is very broad and the latter quite narrow.

Oct 30 •

New York State Department of Financial Services guidance on AI security and governance

What a key regulator is focused on.

Oct 28 •

IQNOX partners with StackAware to strengthen AI governance

Securing the coming wave of AI-powered innovation.

Oct 22 •

Why logging into ChatGPT reduces AI risk

(and why "anonymous" prompting might not be)

Oct 22 •

5 key players in the ISO 42001 certification process

Who's who in the AI governance zoo.

Oct 18 •

3 ways ISO 42001 can help AI-powered companies comply with California's training data transparency bill (AB-2013)

California asserts global jurisdiction over AI.

Oct 16 •

Yes, you are using AI

Pretending otherwise is a security risk.

Oct 13 •

3 business reasons I am staying opted-in to LinkedIn's generative AI training

(and why doing the same might give you a marketing boost)

Oct 9 •

#nojs-banner { position: fixed; bottom: 0; left: 0; padding: 16px 16px 16px 32px; width: 100%; box-sizing: border-box; background: red; color: white; font-family: -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; font-size: 13px; line-height: 13px; } #nojs-banner a { color: inherit; text-decoration: underline; } This site requires JavaScript to run correctly. Please turn on JavaScript or unblock scripts