Loading story…
US policymakers and regulators advanced multiple AI governance initiatives spanning labor-market measurement, standards-setting, and training-data transparency. Nine US senators urged the Department of Labor, the Bureau of Labor Statistics, and the Census Bureau to expand federal surveys (including the Current Population Survey, JOLTS, and the National Longitudinal Survey) to better quantify AI-driven workforce disruption and potential job growth, arguing current public data is insufficient to track AI’s economic impacts.
Separately, a federal judge denied xAI’s attempt to block a California law requiring disclosures about AI training datasets, finding the company did not sufficiently show the disclosures would reveal protectable trade secrets or violate First/Fifth Amendment rights; the case unfolded amid heightened scrutiny of Grok over harmful outputs (including allegations involving antisemitic content and generation of NCII/CSAM). In Washington, a nominee to lead NIST told lawmakers he would prioritize AI metrology and global standards leadership—framing standards as economically and strategically important—while also emphasizing support for advanced semiconductor manufacturing and alignment with the administration’s AI and industrial policy priorities.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
Nine U.S. senators sent a letter to the Department of Labor, Bureau of Labor Statistics, and Census Bureau calling for updated federal surveys and reporting to better measure AI's impact on jobs and the labor market.
At a Senate Commerce, Science and Transportation Committee hearing, Arvind Raman said he would support NIST's AI metrology and standards-setting work, promote U.S. leadership in global AI standards, and prioritize advanced semiconductor manufacturing and manufacturing support programs.
Under the second Trump administration, the former AI Safety Institute was renamed the Center for AI Standards and Innovation, reflecting a lighter-touch regulatory approach to AI policy at NIST.
3 references tracked. Mallory keeps watching after this page renders.
nextgov.com
Open sourcearstechnica.com
Open sourcenextgov.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
U.S. lawmakers introduced and advanced multiple **artificial intelligence policy bills** spanning education, public awareness, and safety requirements. Proposed measures include the *Expanding AI Voices Act* to codify the National Science Foundation’s *ExpandAI* program and broaden AI education and workforce development access (including for minority-serving institutions, rural universities, and first-generation students), and the *Artificial Intelligence Public Awareness and Education Campaign Act* directing the Department of Commerce to run a public campaign on AI risks/benefits, individual rights, identifying AI-generated content, and AI’s prevalence in daily life. Separate legislation was also described that would require **age verification and protections for minors** using AI chatbots. In parallel, the House Foreign Affairs Committee advanced the **AI Overwatch Act**, which would shift greater authority over exports of high-performance, data center-class AI processors to Congress, expanding oversight beyond the Department of Commerce’s Bureau of Industry and Security. The proposal would codify performance thresholds that still allow certain lower-tier accelerators (e.g., Nvidia **H20** and AMD **MI308**) to ship to non-blacklisted entities in adversary nations without a license, while subjecting higher-performance parts (e.g., Nvidia **H200** and AMD **MI325X**) to export controls plus **congressional review/veto**; it would also terminate existing licenses and impose a temporary blanket denial pending submission of a new national security strategy.
Jul 12, 2026
Governments, regulators, and major AI developers moved to formalize oversight of advanced AI systems as concerns grew that frontier and agentic models could accelerate cyberattacks, create liability exposure, and outpace existing governance. In the United States, **NIST** expanded work on AI security through its `AI Agent Standards Initiative`, the `Cyber AI Profile`, and the Commerce Department’s **Center for AI Standards and Innovation (CAISI)**, while Google, Microsoft, xAI, OpenAI, and Anthropic agreed to voluntary pre-release model testing with the government. The White House debated a broader executive order after reports that models such as Anthropic’s **Mythos** and OpenAI’s cyber-focused systems could rapidly identify vulnerabilities and support complex offensive operations; the final order reportedly shortened the review window and paired model access with an AI cybersecurity clearinghouse and vulnerability-sharing measures for critical infrastructure defenders. At the same time, Europe and U.S. states advanced a patchwork of AI governance rules that mixed delayed enforcement with tougher operational expectations. The EU agreed to simplify parts of the **AI Act**, delaying some high-risk obligations while banning nudification tools and preserving strong powers for the Commission’s AI Office over general-purpose AI, even as guidance on high-risk classification and logging requirements continued to emerge. States including Illinois, Utah, Maryland, and San Jose expanded governance-first programs through chief AI officers, sandboxes, incident-investigation frameworks, red teaming, and procurement controls, while insurers, auditors, and legal experts warned that **AI-washing**, weak board oversight, poor logging, and inadequate vendor controls are increasing D&O, regulatory, and tort risk. Across policy, industry, and academia, the direction of travel was toward stronger **auditing, verification, incident reporting, and lifecycle governance** rather than reliance on voluntary model promises alone.
Jul 12, 2026
U.S. policymakers and industry leaders are escalating scrutiny of **AI safety and data protection**, with a particular focus on sensitive data flows and the adequacy of existing guardrails. In a Senate HELP Committee hearing, lawmakers questioned whether federal guardrails are needed to protect Americans’ healthcare data voluntarily uploaded to AI-enabled apps and wearables that may fall outside HIPAA coverage, raising concerns about liability, downstream data use, and integration into medical records; HHS noted it is collecting public input via a request for information on safe and effective AI deployment in healthcare. Separately, commentary on AI governance and safety argues competitive pressure among frontier AI labs can erode safety practices and that clearer antitrust guidance could enable cross-industry collaboration on safety standards without triggering enforcement risk. Tensions over AI “red lines” in national security use also became more public, as **Anthropic** CEO Dario Amodei accused **OpenAI** of misleading messaging about defense work amid reports that Anthropic’s DoD talks faltered over restrictions related to mass domestic surveillance and autonomous weapons, while OpenAI described its agreement as permitting “all lawful purposes” alongside stated prohibitions. Broader, non-incident reporting highlighted enterprise investment to support *agentic AI* (with many data leaders citing governance lagging AI adoption) and general concerns about deepfakes, opaque models, and societal risk; however, several items in the set were primarily newsletters, vendor/industry promotion, or general-interest AI commentary rather than a single, discrete cybersecurity incident or vulnerability disclosure.
Jun 29, 2026