SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Vendor AI Compliance: A Procurement Checklist

0
·2 views

Originally published at https://charz.ai/blog/vendor-ai-compliance-procurement-checklist by Char-Z AI. Buy AI the Way You Buy Software, Then Add the AI Layer Procurement is where third-party AI risk is either controlled or created. A standard software RFI covers security and pricing, but AI tools add dimensions — model behavior, training data, autonomy, and governance — that a traditional RFP misses. This checklist turns the evaluation workflow from our third-party AI risk guide into a concrete, repeatable artifact. Use it in two passes.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

I Read Claude's Biology Discovery as a Pipeline: 5 Lessons

Anthropic posted on September 23 that Claude agents found a new enzyme system hiding in phage DNA. The numbers in the post: roughly 950 agents, 21 hours, 210 million tokens, one giant database of DNA sequences. One agent noticed a repeating pattern next to a gene that looked odd. Humans did the lab work, named the system ART, and released a pre-print. When I checked around 1 PM Singapore time the Hacker News thread sat at 567 points and 588 comments, and most of the fight is about one word: discovery.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

The BIN table said debit. The issuer said credit.

Added card-surcharging logic for a US merchant: debit cards skip the 3% fee, credit cards get it, per the usual state rules. Classification ran off a static BIN range table refreshed quarterly from our processor. Surcharge complaints started trickling in — cardholders insisting their debit card got charged a credit surcharge. Pulled the flagged transactions: roughly 1 in 180 had a BIN that our table listed as credit, but the issuer's own authorization response carried a debit indicator in the response fields. Turns out prepaid and co-branded cards get reissued under ranges that shift between d

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

I Audited the MCP SDK OAuth Fix: 3 Checks Upgrading Misses

Last week the official MCP Python SDK shipped a fix for a credential theft bug, and the fix itself has a trap that a version check will not catch. I was researching the disclosure for my own MCP servers and the remediation notes stopped me cold: patch the package, and part of the vulnerability survives unless you also change how you construct your OAuth providers. Here is the short version. On September 28, a GitHub advisory landed on the modelcontextprotocol python-sdk repo: GHSA-qx49-fqc8-xw99, titled "OAuth client could send credentials to an authorization server chosen by the MCP server."

0 comments Read more at DEV Community