0xCBE

joined 1 year ago
MODERATOR OF
 

cross-posted from: https://infosec.pub/post/397812

Automated Audit Log Forensic Analysis (ALFA) for Google Workspace is a tool to acquire all Google Workspace audit logs and perform automated forensic analysis on the audit logs using statistics and the MITRE ATT&CK Cloud Framework.

By Greg Charitonos and BertJanCyber

 

We’ve made a few changes to the way we host and distribute our Images over the last year to increase security, give ourselves more control over the distribution, and most importantly to keep our costs under control [...]

 

This first post in a 9-part series on Kubernetes Security basics focuses on DevOps culture, container-related threats and how to enable the integration of security into the heart of DevOps.

[–] 0xCBE@infosec.pub 2 points 1 year ago

nice! I didn’t know this plant. I’ll try to find some.

[–] 0xCBE@infosec.pub 1 points 1 year ago

it’s impressive! How does your infrastructure looks like? Is it 100% on prem?

[–] 0xCBE@infosec.pub 8 points 1 year ago (2 children)

I like basil. At some point I i got tired of killing all the plants and started learning how to properly grow and care greens with basil.

It has plenty of uses and it requires the right amount of care, not too simple not too complex.

I’ve grown it from seeds, cuttings, in pots, outside and in hydroponics.

[–] 0xCBE@infosec.pub 1 points 1 year ago

Maybe it's enough to make a pull request to the original CSS files here? I would guess the Lemmy devs would rather focus more on the backend right now

[–] 0xCBE@infosec.pub 1 points 1 year ago (2 children)

great! Have you consider packing this up as a full theme for Lemmy?

[–] 0xCBE@infosec.pub 2 points 1 year ago

nice instance!

[–] 0xCBE@infosec.pub 2 points 1 year ago

I found it interesting because starting from NVD, CVSS etc we have a whole industry (Snyk, etc) that is taking vuln data, mostly refuse to contextualize it and just wrap it in a nice interface for customers to act on.

The lack of deep context shines when you have vulnerability data for os packages, which might have a different impact if your workloads are containerized or not. Nobody seems to really care that much, they sell a wet blanket and we are happy to buy for the convenience.

[–] 0xCBE@infosec.pub 1 points 1 year ago (1 children)

is that so? what's the reason?

[–] 0xCBE@infosec.pub 1 points 1 year ago

ahah thank you, we shall all yell together then

[–] 0xCBE@infosec.pub 1 points 1 year ago (1 children)

This stuff is fascinating to think about.

What if prompt injection is not really solvable? I still see jailbreaks for chatgpt4 from time to time.

Let's say we can't validate and sanitize user input to the LLM, so that also the LLM output is considered untrusted.

In that case security could only sit in front of the connected APIs the LLM is allowed to orchestrate. Would that even scale? How? It feels we will have to reduce the nondeterministic nature of LLM outputs to a deterministic set of allowed possible inputs to the APIs... which is a castration of the whole AI vision?

I am also curious to understand what is the state of the art in protecting from prompt injection, do you have any pointers?

[–] 0xCBE@infosec.pub 3 points 1 year ago

to post within a community

(let me edit the post so it's clear)

[–] 0xCBE@infosec.pub 3 points 1 year ago

👋 infra sec blue team lead for a large tech company

view more: next ›