כולם מדברים על טוויטר אכל למה אף אחד לא דיבר איתי על רדיט.
כל חצי מחשבה שאני זורקת לשם מקבלת מלא פידבק ופרספקטיבות חדשות מאנשים שאשכרה עושים סקיוריטי בפועל.
@LNsry31512 האמת שבדיוק כמו שמעיין תיאר למעלה אני משתמשת בטוויטר כפיד עדכונים ובReddit משתמשת כשאני רוצה להתייעץ או לחפש מידע על משהו ספציפי
אני עושה את זה בדרכ בקהילות security כי זה מה שמעניין אותי :)
@dekel_yako בלוגים שאני כותבת ובא לי לקבל עליהם פידבק מיידי, שאלות מקצועיות כמו איך אתם פותרים אבטחה של x בארגון שלכם
מה שכיף שם זה שאתה מקבל תגובות די מהר והן נורא מפורטות - אם פה הכל קצר שם אנשים ממש ��פרטים
The AI era is redefining network security.
Your team needs fewer handoffs, not more tools, alerts, or manual work.
Learn how to stop threats earlier and protect human and AI workloads with one unified platform
Less fragmentation. Faster protection. See how. https://t.co/eBCdyJ6aZQ
TRUSTED BY DEFAULT 🔑
Third-party integrations make cloud life easier until they become a backdoor.
Working alongside Sentra and Mandiant, our team tracked an active campaign abusing Qubole cross-account trust relationships in AWS. Threat actors leveraged legitimate vendor IAM credentials to roam through multiple customer environments, harvest secrets, and siphon data. Supply chain security is only as strong as the least-restricted trust policy in your graph.
We broke down exactly how the attack unfolded, what indicators to look for in your CloudTrail logs, and how to lock down your third-party roles before your next audit. 🧠
Read the full analysis from Wiz CIRT: https://t.co/xFmR7wAfEk
What people don't know is that - frontier LLMs are not "defending customers”, they are exposing vulnerabilities - defense means - no false positives, comprehensive coverage, and a cost efficient solution. Any defense involves, sensors, inline inspection and enforcment, this can only come with a collaborative approach.
It's time for frontier LLMs to take a responsible approach to Cyber. I have been watching them consistently tout their abilities on finding vulnerabilities and daisy chaining them to be able to attack enterprises. I have also recently learnt about their efforts to create synthetic data to enhance their capabilities. I am all for it. But don't use this as a tactic to require each enterprise to scan for vulnerabilities again.
The narrative needs to change - we already know that we are in a cycle where all enterprises need to remediate their vulnerabilities. It is important to understand:
1. Vulnerability discovery is existential, because bad actors will - patching it is even more so. Expending efforts at more vulnerability discovery needs to be balanced with a solve.
2. LLMs are capable of recommending patches, but before a patch is developed, and deployed, it needs to be tested in its environment to ensure continued functioning of the application, and even now the solve has high false positives. No enterprise can do it all at speed.
3. Despite their enhanced capability, there is still significant difference in what vulnerabiities are found across all their Frontier LLM's, so customers will need to test across a multi-model harness. One LLM isn't the solution.
4. Most organizations do not have capacity to patch at the speed needed, especially the smaller ones.
5. We don't talk about operational technology enough, most critical infrastructure relies on OT and we need a solve for them in addition to Open Source.
The most obvious solution is virtual patching. This is a time tested technology that is currently available with cyber vendors for endpoints, WAF, cloud, network use cases. It also is not comprehensive enough currently, we need to scale this fast. We need a vulnerability clearing house and fast signature development for all these vulnerabilites to respond at speed across our industry.
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: https://t.co/wzNkwHs7IN