“And so in Request Rocket, what we also have is the ability to drop in an authorization layer that says this user or this particular request is either allowed or denied based on certain criteria that we can configure in the platform.”

Risky Business · Snake Oilers: Minimal.dev, Request Rocket and TRM Labs

Play from 21:13
21:13

Audio streams from the publisher’s own feed. Verbatim does not host or copy it.

What was described

added a deterministic predicate-based rule system to authorize each request based on the caller’s identity and requested API parts

Said nearby on the same subject

“We spun up a bunch of little go processes that would each establish a WebSocket connection and run through a series of API requests that made it look like they were actual clients.”
♫
Said on The Pragmatic Engineer
Why it worked Share this moment
“We are giving identity and access to agents based on the task… we call this CASA, which is continuous semantic authorization and giving access based on that.”
CO
Cisco Outshift team
DataFramed ·
Why it worked Share this moment
“We're getting about, um, 30 requests per second of people that are pulling that data and building it into their own system.”
♫
Said on Lawyerist Podcast
Hard number 30 requests per second Share this moment
“We got a decent response to the request for an audit, the request for information really from our different agencies... there is a second effort going on right now to sharpen the fidelity around that and get the numbers tighter”
♫
Said on What Bitcoin Did
Why it worked Share this moment

Moments like this, every Monday

The strongest new moments on your topics, in the speakers' own words. Free for three topics.

No card. No password. One-click unsubscribe.

Track a competitor?

Pro watches up to 25 names or phrases and emails you the morning after they are said.

See Pro, $29 a month

Verbatim quotes a short extract and links to the episode; the episode belongs to its publisher. Remove a show.