惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
aimingoo的专栏
aimingoo的专栏
D
Docker
N
Netflix TechBlog - Medium
IT之家
IT之家
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
宝玉的分享
宝玉的分享
美团技术团队
P
Proofpoint News Feed
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Stack Overflow Blog
Stack Overflow Blog
The Cloudflare Blog
G
Google Developers Blog
腾讯CDC
Help Net Security
Help Net Security
Google DeepMind News
Google DeepMind News
Security Archives - TechRepublic
Security Archives - TechRepublic
Apple Machine Learning Research
Apple Machine Learning Research
L
LINUX DO - 最新话题
O
OpenAI News
博客园 - 司徒正美
Google Online Security Blog
Google Online Security Blog
H
Hacker News: Front Page
博客园 - 聂微东
Recent Commits to openclaw:main
Recent Commits to openclaw:main
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Project Zero
Project Zero
Vercel News
Vercel News
C
CXSECURITY Database RSS Feed - CXSecurity.com
C
Check Point Blog
Application and Cybersecurity Blog
Application and Cybersecurity Blog
A
Arctic Wolf
Microsoft Security Blog
Microsoft Security Blog
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Forbes - Security
Forbes - Security
www.infosecurity-magazine.com
www.infosecurity-magazine.com
人人都是产品经理
人人都是产品经理
大猫的无限游戏
大猫的无限游戏
S
Security @ Cisco Blogs
T
Tor Project blog
D
DataBreaches.Net
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Spread Privacy
Spread Privacy
W
WeLiveSecurity
V2EX - 技术
V2EX - 技术
Simon Willison's Weblog
Simon Willison's Weblog
AI
AI
Security Latest
Security Latest
S
Securelist

Wiz Blog | RSS feed

Meet Wiz for M365: Bringing SaaS into the Security Graph Bringing Security Visibility to Vercel with Wiz Axios NPM Distribution Compromised in Supply Chain Attack Tracking TeamPCP: Investigating Post-Compromise Attacks Seen in the Wild The Wiz Blue Agent, now Generally Available Beyond the Badge: What Achieving Microsoft’s Certified Software Designation Means for Your Cloud Security Introducing the Green Agent: AI-Powered Remediation for the Cloud Three’s a Crowd: TeamPCP trojanizes LiteLLM in Continuation of Campaign KICS GitHub Action Compromised: TeamPCP Strikes Again in Supply Chain Attack Introducing the Wiz Red Agent- AI-Powered Attacker Introducing Wiz AI Application Protection Platform (AI-APP) Introducing Wiz Agents & Workflows: Security at the Speed of AI AI Runtime Threat Detection: From Input to Real-World Impact Trivy Compromised: Everything You Need to Know about the Latest Supply Chain Attack It’s Official: Wiz Joins Google Understanding and Reducing AI Risk in Modern Applications Introducing Wiz Tenant Manager: Multi-Tenant Management for Federated Organizations The Agile FedRAMP Playbook, Part 4: Reactive Risk Management through Enriched Incident Response Wiz Achieves CPSTIC Certification in Spain Seeing AI Clearly: Building Visibility Across Modern AI Applications The Agile FedRAMP Playbook, Part 3: Preventative Risk Management by building Secure by Design Wiz Leads the 2026 Latio Application Security Report with awards in 4 categories Building an Agentic Cloud Security Ecosystem: A Reference Architecture with Wiz MCP and Infosys Cyber Next The Agile FedRAMP Playbook, Part 2: Proactive Risk Management with Continuous Monitoring Cloud-native Security for your Windows environment: Announcing the Wiz Runtime Sensor for Windows Would You Click ‘Accept’? Automatically detecting malicious Azure OAuth applications using LLMs Wiz Named a Leader in The Forrester Wave™: Cloud Native Application Protection Solutions, Q1 2026 From Detection to Remediation: It’s Time to Rethink AppSec Around Exploitability and Root Cause Fixes The Agile FedRAMP Playbook, Part 1: Why Risk is Your Best Starting Point Introducing AI Cyber Model Arena: A Real-World Benchmark for AI Agents in Cybersecurity Wiz + Spotify Backstage: Security at the Developer’s Desk Building AI Security Together: New Ways to Partner with Wiz for AI Security in 2026 Hacking Moltbook: The AI Social Network Any Human Can Control The Year in Wiz Research: 2025 Most Read Blogs WizExtend is Here: AI and Cloud Security Insights in Your Daily Workflow From Detection to Remediation: Wiz in Your JetBrains IDE Agentic Browser Security: 2025 Year-End Review CodeBreach: Infiltrating the AWS Console Supply Chain and Hijacking AWS GitHub Repositories via CodeBuild A 90-Day Action Plan to Turn Resolutions into Results with Wiz Introducing the Wiz Partner Alliance: A New Chapter for Partner Success Preparing for Post-Quantum Cryptography Wiz Recognized as a 2025 Customers’ Choice in the Gartner® Peer Insights™ Voice of the Customer for CNAPP Expanding the Zero Critical Club to set a new standard for AppSec and SecOps teams Snipping the Long Tail of Shai-Hulud 2.0 Protecting Against Zero-Day Vulnerabilities with SOC-Level ASM Alert MongoBleed (CVE-2025-14847) exploited in the wild: everything you need to know The Kenna Transition: Your Strategic Shift to Exposure Management From MCP to Vibe Coding: Full Endpoint Visibility in Wiz AI Security Bringing Oracle Cloud Identity to Wiz Zero‑Days in the Age of AI: Behind the Scenes of ZeroDay.cloud 2025, with a Record High of CVEs in Critical Cloud Infra Gogs 0-Day Exploited in the Wild Code to Cloud Attacks: From Github PAT to Cloud Control Plane Top AWS re:Invent Announcements for Security Teams in 2025 React2Shell: Technical Deep-Dive & In-the-Wild Exploitation of CVE-2025-55182 React2Shell (CVE-2025-55182): Everything You Need to Know About the Critical React Vulnerability Wiz Product Announcements at re:Invent 2025: Expanding Visibility from Code to Cloud Introducing Wiz SAST: Where Code Risk Meets Cloud Context Wiz Becomes Fastest Security ISV to Reach $1 Billion in AWS Marketplace Lifetime Sales It's Here! Wiz Exposure Management is Now GA Shai-Hulud 2.0 Aftermath: Trends, Victimology and Impact Service Catalog is Here: Expand Risk Visibility for Your Service and Its Dependencies, Simplify Issue Ownership WizOS: Powering Secured Image Adoption with AI 3 OAuth TTPs Seen This Month — and How to Detect Them with Entra ID Logs Mastering Software Governance with Hosted Technologies Inventory Shai-Hulud 2.0 Supply Chain Attack: 25K+ Repos Exposing Secrets Get Certified on Wiz Defend for Threat Detection and Response Blueprint for Security: A Guide to Code, Governance, and Response Frameworks Google Unified Security Recommended Program Names Wiz Among First 3 Strategic Partners Introducing Posture Issues: Transform Security Findings into Actionable Outcomes Empower and Accelerate Your SOC with the Blue Agent Exposure Report: 65% of Leading AI Companies Found with Verified Secret Leaks Wizdom 2025 Product Announcements: Extending the Cloud Operating Model When AI Becomes the Heart of Security: Powering a Future You Can Trust AI-Powered Wiz: From Agents to Everyday Intelligence Defend Agentless Workload Detection: Bringing Visibility to Blind Spots in Threat Detection Securing AI Agents with Wiz AI-SPM Introducing Wiz ASM: Context-Driven Attack Surface Management Securing Critical Infrastructure in the Cloud Era: A Policy and Technology Blueprint How CISOs Should Plan Security Budgets for 2026 Beyond the Checkbox: How Wiz Transforms SOC 2 into a Security Powerhouse Bringing Visibility to Kubernetes: Unified Inventory and Network Insight The Foundation Modern AppSec Is Still Missing: Code to Cloud, Rebuilt the Right Way Dismantling a Critical Supply Chain Risk in VSCode Extension Marketplaces Introducing HoneyBee: How We Automate Honeypot Deployment for Threat Research RediShell: Critical Remote Code Execution Vulnerability (CVE-2025-49844) in Redis, 10 CVSS score Defending against database ransomware attacks AI Security 101: Mapping the AI Attack Surface Introducing zeroday.cloud: First-of-its-kind cloud and AI hacking competition Unifying Cloud Risk and Network Defense: Wiz and Check Point The emerging use of malware invoking AI Wiz achieves FedRAMP High authorization Wiz + HCP Terraform: Close the IaC-to-Cloud Infrastructure Security Gap IMDS Abused: Hunting Rare Behaviors to Uncover Exploits Beyond CVEs: The Exploitation of Everyday Misconfigurations Wiz Research Discovers One in Five Organizations Exposed to Systemic Risks in Vibe-Coded Applications - Here's How to Secure Them Introducing Wiz Incident Response: Your Expert Partner for Cloud Security Incidents Shai-Hulud: Ongoing Package Supply Chain Worm Delivering Data-Stealing Malware DORA Compliance in the Cloud Era: Insights from Deloitte and Wiz How Wiz Customers like Brex and FICO See AI Changing Security Wiz Recognized as a Leader in the 2025 IDC MarketScape for ASPM
Biden's AI Executive Order: What it says, and what it means for security teams
Joseph Thacker · 2023-11-22 · via Wiz Blog | RSS feed

The 2023 Executive Order on AI (order number 14110), issued by President Biden, has far-reaching implications for companies relying on AI. It establishes a new set of standards for AI safety and security, privacy protection, and equitable use. This is a significant moment for AI in America and its impact will be felt by privacy and security teams. In most organizations, protecting privacy falls on the shoulders of the security team, so security teams specifically need to understand what this order means for them.

Practical Explanations of Key Points 

First, we’ll go over the key points with a relevant quote and discuss the implications. Then we’ll cover the practical themes that run throughout the entire Executive Order. Let’s begin!

The All-Encompassing Directive

“Develop standards, tools, and tests to help ensure that AI systems are safe, secure, and trustworthy. The National Institute of Standards and Technology will set the rigorous standards for extensive red-team testing to ensure safety before public release. The Department of Homeland Security will apply those standards to critical infrastructure sectors and establish the AI Safety and Security Board. The Departments of Energy and Homeland Security will also address AI systems’ threats to critical infrastructure, as well as chemical, biological, radiological, nuclear, and cybersecurity risks. Together, these are the most significant actions ever taken by any government to advance the field of AI safety.”

The section above is the most descriptive, tactical, and comprehensive for  security teams. Any organization developing AI features or systems will need to comply with the upcoming NIST standards, so they should immediately begin putting processes in place to do so. The wording implies that the standards will require testing the systems to ensure they are safe, secure, and trustworthy. As those terms are ambiguous until NIST unveils their AI standards, a best-effort start on the testing program is a step in the right direction.

The action item here is "extensive red-team testing." Red-teaming has become a widely-used term with a lot of definitions in the age of AI, so we'll break it down in the "testing" section below. 

If your company falls into any of the categories listed in the follow-up sentences of this directive, you'll need to comply with the respective governmental organizations' directions. The distinction is vague, but it appears that Critical Infrastructure as well as chemical, biological, radiological, nuclear, and cybersecurity risks will work with Homeland Security, while anything pertaining to "energy" in that list will work with the Department of Energy.

Privacy

"Protect Americans’ privacy by prioritizing federal support for accelerating the development and use of privacy-preserving techniques—including ones that use cutting-edge AI and that let AI systems be trained while preserving the privacy of the training data."

This directive emphasizes the importance of privacy in the era of AI. It says that companies making AI applications must prioritize privacy-preserving techniques. For security teams, this means a significant shift in focus towards privacy-centric practices. These teams will need to model potential threats that could impact user privacy and develop strategies to mitigate these risks.

In practical terms, this could involve a review of AI systems to assess their privacy measures. Security teams may need to collaborate closely with their AI developers to understand the intricacies of their AI systems and identify potential privacy vulnerabilities. This may also mean staying up to date with the latest adversarial attacks that specifically target privacy and keeping track of the evolving definitions of what constitutes "private information."

Investing in privacy-related training might be necessary to equip security teams with the skills and knowledge necessary to tackle these new challenges. Along with that, a potential implication is the need for transparency. Security teams may have to push for communication with users of how their data is being used and protected, which could involve developing user-friendly privacy policies and consents.

The business benefits of implementing these practical strategies are significant. Beyond complying with the Executive Order, by prioritizing user privacy, companies will build stronger relationships with their customers due to their focus on trust and transparency.

Workforce 

"Develop principles and best practices to mitigate the harms and maximize the benefits of AI for workers by addressing job displacement; labor standards; workplace equity, health, and safety; and data collection. These principles and best practices will benefit workers by providing guidance to prevent employers from undercompensating workers, evaluating job applications unfairly, or impinging on workers’ ability to organize."

This order addresses the impact of AI on the workforce. It's a clear recognition of the transformative power of AI and its potential to disrupt traditional work structures and processes. 

Security teams will need to investigate and test any software that uses AI to determine compensation and handle job applications or that affects workers' ability to organize.  This could mean digging into the ethical implications of using AI to monitor employee behavior (in case it could inhibit their ability to organize), or it could involve working with HR to develop policies for using AI in hiring or performance evaluation.

Data collection is another potential focus area. Security teams might need to ensure that any data collected by AI systems is done in a way that respects employees' privacy and is compliant with data protection laws. This could involve implementing robust data governance policies and procedures, and ensuring that all data collected is securely stored and appropriately used.

Besides testing AI systems, the job displacement, labor standards, workplace equity, health, and safety issues are outside the scope of the security team for most organizations. Overall, the impact of this section affects organizations less than the privacy and all-encompassing portions above.

Healthcare 

"Advance the responsible use of AI in healthcare and the development of affordable and life-saving drugs. The Department of Health and Human Services will also establish a safety program to receive reports of—and act to remedy – harms or unsafe healthcare practices involving AI."

This portion of the Executive Order has significant implications for security teams at companies that are developing AI for use in healthcare. These teams will need to ensure that their AI systems are not introducing additional risks to their patients. This could involve implementing security measures to protect patient data and placing guardrails on AI systems, or it could mean working closely with healthcare providers to ensure that AI tools are used responsibly.

The healthcare industry is often lagging in advancements when it comes to cybersecurity, so it may be a significant challenge. Furthermore, the second sentence outlines a path for unsafe practices to be reported; this emphasizes how serious the administration is about enforcing the executive order in the healthcare industry.

Additionally, security teams may need to work closely with other stakeholders in the healthcare sector, including healthcare providers and regulatory bodies. This collaboration could involve sharing best practices or developing new standards for the use of AI in healthcare, so keeping up to date with current regulations and training staff will be important.

Criminal Justice

"Ensure fairness throughout the criminal justice system by developing best practices on the use of AI in sentencing, parole and probation, pretrial release and detention, risk assessments, surveillance, crime forecasting and predictive policing, and forensic analysis. The Department of Health and Human Services will also establish a safety program to receive reports of—and act to remedy – harms or unsafe healthcare practices involving AI."

This directive is primarily aimed at the criminal justice system, but it has implications for any company using or developing AI for surveillance or predictive analytics. Security teams at these companies will need to ensure that their AI systems are not only secure but also fair. This could involve implementing new testing procedures to check for bias in those AI systems, or it could mean working with legal experts to ensure that AI tools are used in a way that respects people's constitutional rights.

The use of AI in surveillance and predictive analytics has been a contentious issue. While AI can enhance the capabilities of these systems, it also raises significant ethical and legal concerns. This directive from the executive order is a clear call to action for security teams to address these concerns head-on.

For companies using AI in surveillance, this could mean a thorough review of any system used to identify individuals or patterns of behavior. Bias in these systems can lead to unfair targeting of certain groups, infringing on their rights to privacy and potentially leading to legal repercussions. Security teams will need to work closely with AI developers and legal experts to ensure these systems are as unbiased as possible.

Predictive analytics, particularly in the context of the criminal justice system, also present significant challenges. These systems are often used to predict the likelihood of recidivism or to assist in sentencing decisions. However, if these systems are biased, they can lead to unjust outcomes. Security teams will need to implement rigorous testing procedures to identify and mitigate any bias in these systems.

Landlords and Contractors

"Provide clear guidance to landlords, Federal benefits programs, and federal contractors to keep AI algorithms from being used to exacerbate discrimination."

This directive is particularly relevant if your company is involved in landlord-tenant issues or if it employs federal contractors. The aim here is to prevent AI from being used in a discriminatory way. This is a significant step towards ensuring fairness and equity in AI applications, particularly in areas where AI has the potential to significantly impact individuals' lives, such as housing and employment.

Similar to some previous sections, for security teams, this directive presents a unique challenge. It's not enough to ensure that the AI systems the company uses are secure; they must also be free from discriminatory bias. This is a complex task that goes beyond traditional security measures. It requires a good bit of understanding how AI models work, how they can inadvertently lead to discriminatory outcomes, and how to test for it. Many teams may need to hire — or work closely with — external data scientists to ensure that the AI models being used are being tested for bias. 

Furthermore, security teams may need to develop strategies to mitigate any identified biases. This could involve fine-tuning them, filtering output that is biased, or changing models altogether. It could also involve implementing safeguards such as setting thresholds for decision-making that ensure fairness.

Finally, security teams will need to ensure that these measures are not just implemented, but also maintained over time. This could involve regular audits and updates to the AI systems and ongoing training for staff to ensure that they are aware of the importance of fairness and non-discrimination in AI.

The Major Themes

The Executive Order represents a massive moment in the AI industry, particularly for security teams. It's a call to action that necessitates a shift in focus and a deeper understanding of the implications of AI within applications. The world is still adjusting to the breakthroughs in AI — even as adoption skyrockets — so while [RR7] the government may be gracious initially, this is a heavy lift for most companies. They need to get ahead of it. The major themes of how to comply with the Executive Order for most security teams are outlined below. 

Training

The Executive Order requires a wide variety of changes. There will be a great need for training in most organizations. Security teams will need to understand the nuances of how different AI systems and models work. They'll also have to understand how features like web search, document retrieval, and third-party plugins work. Additionally, they'll have to understand the different ways these features can be exploited. They'll need training on how prompt injection can be used by adversaries. This includes understanding what constitutes privacy, how to protect it, and how to defend against attacks that target privacy specifically.

Security teams will also need to understand the regulations their organizations are under and how to comply with them. The requirements and directives will likely change over time as society develops alongside AI functionality, so ongoing education will be necessary as well.

Knowledge Sharing

The Executive Order underscores the importance of staying informed. As we covered in the Training section, security teams need to understand what is required of them  and know who they're accountable to. Staying up to date with regulations will be critical. As the government announces new AI standards, security teams need to ensure they're compliant. This could involve regular reviews of the company's AI practices and procedures to ensure they align with the latest regulations.

Security teams also need to understand what their companies are building and how it's being used. This should include regular communication with the AI developers at their organizations — and other stakeholders — to stay updated on AI projects. The new features and systems should go into a continuous testing cycle for most organizations. And on the topic of testing...

Testing

Testing is a significant theme in the Executive Order. It states that building AI systems is not enough; but that these systems should be extensively tested to ensure they're safe, secure, and trustworthy. This involves implementing testing procedures, including red teaming, to identify potential vulnerabilities.

Red teaming is a form of testing where a group of security professionals, known as the red team, mimic potential attackers to find vulnerabilities in a system. In the context of AI, this usually means attempting to get the AI models to return content that they shouldn't, in the form of output that is biased, explicit, or harmful. Thankfully, it seems that the industry is adopting the practice of simulating adversarial attacks on AI systems to test their robustness and security.

Since testing extends to fairness and non-discrimination, security teams need to ensure that their AI systems are fair. This isn't something security teams have focused on in the past, so there will likely be a learning curve. It may mean implementing new testing procedures to check for bias in an automated fashion.

Collaboration

The Executive Order highlights the need for collaboration and transparency. Security teams will need to work closely with AI developers, industry providers, regulatory bodies, and other stakeholders. This collaboration could involve sharing best practices, developing new standards, or working together to address shared challenges. Collaboration requires good communication, so having a policy outlining the best communication channel and guidelines for response times would be beneficial.

Conclusion

The Executive Order issued by President Biden represents a significant shift in the way AI is regulated in America. For security teams at companies using AI, it presents a range of new challenges and opportunities. AI unlocks tremendous innovation, and it also requires security teams to adapt their systems and processes so they can secure the AI pipelines and protect against AI misconfigurations and vulnerabilities. By understanding the implications of these directives, security teams can ensure that their use of AI is not only secure but also ethical and compliant with the new standards.

See for yourself...

Learn what makes Wiz the platform to enable your cloud security operation