NixOS
0xCBE
1 year ago
•
100%
You build a derivation yourself... which I never do. I am on mac so I brew install and orchestrate brew from home manager. I find it works good as a compromise.
boringappsec.substack.com
orca.security
blog.mithrilsecurity.io
github.com
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](https://www.linkedin.com/in/charitonos/) and [BertJanCyber](https://twitter.com/BertJanCyber)
www.chainguard.dev
>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.
www.wiz.io
apnews.com
Gardening
0xCBE
1 year ago
•
100%
nice! I didn’t know this plant. I’ll try to find some.
0xCBE
1 year ago
•
100%
it’s impressive! How does your infrastructure looks like? Is it 100% on prem?
0xCBE
1 year ago
•
100%
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.
www.felipecruz.es
securitylabs.datadoghq.com
www.forbes.com
Not really technical, but gives some pointers to wrap your head around the problem
www.theregister.com
"Toyota said it had no evidence the data had been misused, and that it discovered the misconfigured cloud system while performing a wider investigation of Toyota Connected Corporation's (TC) cloud systems. TC was also the site of two previous Toyota cloud security failures: one identified in September 2022, and another in mid-May of 2023. As was the case with the previous two cloud exposures, this latest misconfiguration was only discovered years after the fact. T**oyota admitted in this instance that records for around 260,000 domestic Japanese service incidents had been exposed to the web since 2015**. The data lately exposed was innocuous if you believe Toyota – just vehicle device IDs and some map data update files were included. "
airisk.io
"database [...] specifically designed for organizations that rely on AI for their operations, providing them with a comprehensive and up-to-date overview of the risks and vulnerabilities associated with publicly available models."
securitylabs.datadoghq.com
This is an excellent series on container security fundamentals by Rory McCune who is a bit of an authority in this field: * [part 1](https://securitylabs.datadoghq.com/articles/container-security-fundamentals-part-1/) * [part 2](https://securitylabs.datadoghq.com/articles/container-security-fundamentals-part-2/) * [part 3](https://securitylabs.datadoghq.com/articles/container-security-fundamentals-part-3/) * [part 4](https://securitylabs.datadoghq.com/articles/container-security-fundamentals-part-4/)
Very useful collection of security incidents involving public clouds
www.wiz.io
(I am not fond on vendor's blogs as the signal to noise ratio is very low, since they are written to please search engines more than engineers... but Scott Piper gets a pass.) I found this insightful, access keys are such a liability that is better to tame as early as possible. Fixing the problem a scale is a lot more challenging.
[@jerry@infosec.pub](https://infosec.pub/u/jerry) I took the liberty to promote this instance a bit [here](/c/newcommunities@lemmy.world), the post is [this one](https://infosec.pub/post/73504). I'd like to help growing a community, is there anything we could do?
👋 we have a bunch of cybersecurity/infosec/security engineering focused communities going on at https://Infosec.pub - an instance mostly dedicated to security professional and people interested in the field. The instance is run by the same good folks of https://infosec.exchange Come and join: * [Blue Team](/c/blueteam@infosec.pub) * [Red Team](/c/redteam@infosec.pub) * [AI Security](/c/ai_infosec@infosec.pub) * [Cloud Security](/c/cloudsecurity@infosec.pub) and [more](https://infosec.pub/communities)
Chat
0xCBE
1 year ago
•
100%
nice instance!
Cloud Security
welcome
0xCBE
1 year ago
•
100%
ahah thank you, we shall all yell together then
AI Infosec
In Escalating Order of Stupidity
0xCBE
1 year ago
•
100%
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?
Is there a way to enforce certain templates on submissions within a community? I was fighting a holy crusade against content marketers on r/cloudsecurity and I required to have submission statements. Is there a way to do something similar on here? Should I implement a bot of some sort?
👋 Hello all! So, how big is your security organization and how are responsibilities split across teams? I've been through I don't know how many reorgs and seen quite a few place, and while some patterns emerge it's always interesting to see how Security is split up. In my current company we evolved from: - 6ppl: one security team - ~12ppl: one security team, distributed between two locations - ~12ppl: infrasec team, appsec team - ~30ppl: infrasec team, dir team, appsec team, risk/audit team - ~60ppl: infrasec team, dir team, corpsec team, appsec tooling team, appsec consulting team, risk/audit team, compliance team
0xCBE
1 year ago
•
100%
👋 infra sec blue team lead for a large tech company
Hi all, I am the moderator of r/cloudsecurity Following the reddit controversy I've closed the subreddit and started moving it here. You are very welcome to join and contribute!