Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

rotating env vars - automatically converts non-sensitive to sensitive guardrails to prevent mistakes: - checks if dev value matches prod/preview - educates that revoking is still needed - bunch of heuristics on key name/value for mistakes collab w William Bout

11,399 görüntüleme • 6 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

I had a good meeting with U.S. Special Presidential Envoy, General Keith Kellogg Keith Kellogg. Ukraine is deeply grateful to the United States for its support, and we value that President Trump President Donald J. Trump is so determined to achieve real peace. It is very important to realize all the results—political, defense, and economic—that were achieved during our meeting together with European leaders in Washington. Undoubtedly, it was a successful Summit, a demonstration of true unity between Europe and America. Ukraine, as always, is uniting the world. We value the United States’ readiness to be part of the security architecture for Ukraine, and our teams are actively working on shaping it. We expect that the key foundations of security will be defined shortly. We discussed how we can influence the Russians, compel them to engage in real negotiations, and end the war. Sanctions, tariffs—everything must remain on the agenda. We are ready to engage in a format of leaders. This is the format needed to resolve the key issues. Now, the same readiness is needed from Moscow. Military cooperation is important for both Ukraine and the United States, and there are two strong opportunities—an agreement on arms procurement and an agreement on drones that could significantly strengthen our arsenals. We are maintaining momentum in our work within PURL. This is an important instrument for procuring American equipment funded by partners, and we are now actively working on engaging additional countries. And, of course, the humanitarian track. The return of all abducted children. We strongly hope that America, President and the First Lady of the United States First Lady Melania Trump will continue to make personal efforts to bring back all children illegally abducted by Russia. Thank you!

Volodymyr Zelenskyy / Володимир Зеленський

171,139 görüntüleme • 1 yıl önce

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 görüntüleme • 7 ay önce

It is spectacularly easy to get shadowbanned on X One wrong reply and your reputation can go up in flames Luckily there are a few steps you can take to reduce your odds of getting banned by 10x 🔶First step: Don't reply from notifications Notifications are a minefield because hidden, spammy replies are shown to you as normal replies It's never worth replying from here. You risk replying to low reputation accounts without even knowing it Just reply normally from the posts so you know what's marked as spam 🔶Second step: turn off sensitive content in your settings Engaging with sensitive content could hurt your reputation score Little do you know, but a ton of content that’s not actually sensitive, gets marked as sensitive Turn off sensitive content in your settings, then become shocked when you see how much innocent content is marked as sensitive (tutorial video below) 🔶Third Step: Check for following/follower ratio before hitting reply Easy check to take before every reply This is brought up in the code 100 different times as a reputation destroyer Make sure to hover over people’s name before replying and check for their ratio 60% followers to following is the ratio cut off point 🔶Fourth Step: Don’t feed the trolls There are 100+ labels for toxic behavior in the code Engaging with anyone with these labels hurts your reputation For some of these labels they can be applied just for “insults” Best not to engage with any trolls (also good for your mental health) 🔶Fifth Step: Get the blue checkmark The easiest step of them all It’s coded into the algo that if you have the blue checkmark you can’t be marked as spam Yes it costs money, but if you have any serious interest of growing on this platform, it’s a must have 🔶🔶🔶🔶🔶 I've said this before, but it absolutely stinks you have to take all these steps just to get some reach At times, it can be like walking in a minefield It doesn't exactly make a social media platform feel very 'social' I have high confidence Elon is working to fix this. He's mentioned it before. But in the meantime, take these steps and be careful. It's worth it if you care about being seen on this platform. I'm 100% confident brighter days are ahead. Let me know below if any of these tips helped and what other steps you take to avoid getting banned.

Alex Finn

300,203 görüntüleme • 3 yıl önce