skuenzli

This is the motivating example I was looking for on the readme: a client making a request and an agent handling it using the MCP. Along with a log of the agent reasoning its way to the answer.

Thank you - that's helpful.

Thank you - I appreciate the background.

I'll reach out to the email address in your profile.

Do you have any suggestions for finding firm or attorney that can help with immigration of health care workers, specifically nurses?

I have a friend searching for such a firm now and of the ~15 firms contacted none had any experience with health care immigration.

They have decades of experience with IT services and the path to H1-B for IT.

If no suggestions, can you share thoughts on why healthcare immigration attorney help seems to be difficult to find?

Dumping audit reports with a sea of red on delivery teams for things largely low-risk in reality and out of their control rarely does any good.

I'm not up on EKS-ELB these days, but if the nodes only allow ingress to NodePorts from the ELB, then it seems like those findings should be suppressed in most orgs.

If the SecEng team was partnering with the delivery team they'd know that before sending the report.

Thanks for the additional context.

Agree that leaders should definitely be ready to motivate stakeholders and collaborating teams to act on this kind of info before spending significant time gathering & producing it.

Can you share what the high-level goal of the project was?

i.e. was the VP trying to reduce risk? scale out responsibility for managing access?

I love this approach to integrating access control workflow into existing workflows using code.

Really feels like security can actually be "everyone's job" when you're able to make good access management decisions from within your existing tools and their supporting context.

(Author & k9 Security Founder)

Thanks for taking a look at our Terraform module designed to help Cloud teams protect data in AWS S3, quickly and confidently. Feedback appreciated :)

We are trying to improve the usability of Cloud security.

Specifically, we've heard that the AWS security model is too complex and difficult to validate.

Configuring a least privilege bucket policy is amongst the most difficult AWS security challenges and a problem we're trying to solve for non-security experts.

Do you feel like this module makes it easy to understand what access the author intends to grant? What makes that difficult?

Thanks!

Stephen

(Author) The `riskquant` tool is really cool and the library is even cooler. I'm excited that tech folks are starting to quantify risks for their quickly changing systems.

Risk management in tech/cybersecurity is really immature compared to other domains like structural engineering (earthquakes), finance (portfolio risk position), or environmental health and safety.

riskquant and similar tools do the critical work of making proven risk analysis methods accessible in delivery pipelines and deployment platforms for inclusion in continuous risk monitoring systems and scaling periodic risk analysis activities.

Thanks Jay, that means a lot coming from you. I hope we get to build great things together again some day.