<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>National Security | Interactive News</title>
	<atom:link href="https://111things.com/tag/national-security/feed/" rel="self" type="application/rss+xml" />
	<link>https://111things.com</link>
	<description>Ask follow up questions &#38; get instant answers and insights.</description>
	<lastBuildDate>Sat, 29 Aug 2026 06:27:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://i0.wp.com/111things.com/wp-content/uploads/2026/06/111things-apple-touch-icon-180-1.png?fit=32%2C32&#038;ssl=1</url>
	<title>National Security | Interactive News</title>
	<link>https://111things.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">126483067</site>        <div class="get111-archive-chat" data-get111-context="tag" data-get111-bot="default" data-get111-autosend="1" data-get111-term="national-security" data-get111-term-name="National Security">
            <div class="get111-archive-chatbot">
                <div class='mwai-chatbot-container' data-params='{&quot;customId&quot;:&quot;get111-archive-tag-default&quot;,&quot;aiName&quot;:&quot;The 111: &quot;,&quot;userName&quot;:&quot;User:&quot;,&quot;guestName&quot;:&quot;Guest:&quot;,&quot;textSend&quot;:&quot;Send&quot;,&quot;textClear&quot;:&quot;Clear&quot;,&quot;imageUpload&quot;:false,&quot;fileUpload&quot;:false,&quot;multiUpload&quot;:false,&quot;maxUploads&quot;:1,&quot;fileUploads&quot;:0,&quot;mode&quot;:&quot;chat&quot;,&quot;textInputPlaceholder&quot;:&quot;Ask me anything&quot;,&quot;textInputMaxLength&quot;:12000,&quot;textCompliance&quot;:&quot; &quot;,&quot;startSentence&quot;:&quot;&quot;,&quot;localMemory&quot;:true,&quot;themeId&quot;:&quot;foundation&quot;,&quot;window&quot;:false,&quot;icon&quot;:&quot;&quot;,&quot;iconText&quot;:&quot;&quot;,&quot;iconTextDelay&quot;:1,&quot;iconAlt&quot;:&quot;AI Engine Chatbot&quot;,&quot;iconPosition&quot;:&quot;bottom-right&quot;,&quot;centerOpen&quot;:false,&quot;width&quot;:&quot;&quot;,&quot;openDelay&quot;:&quot;&quot;,&quot;iconBubble&quot;:false,&quot;windowAnimation&quot;:&quot;zoom&quot;,&quot;fullscreen&quot;:false,&quot;copyButton&quot;:false,&quot;pdfButton&quot;:false,&quot;headerSubtitle&quot;:&quot;Discuss with&quot;,&quot;containerType&quot;:&quot;standard&quot;,&quot;headerType&quot;:&quot;standard&quot;,&quot;messagesType&quot;:&quot;standard&quot;,&quot;inputType&quot;:&quot;standard&quot;,&quot;footerType&quot;:&quot;standard&quot;}' data-system='{&quot;botId&quot;:null,&quot;customId&quot;:&quot;get111-archive-tag-default&quot;,&quot;userData&quot;:null,&quot;sessionId&quot;:null,&quot;restNonce&quot;:null,&quot;contextId&quot;:null,&quot;pluginUrl&quot;:&quot;https:\/\/111things.com\/wp-content\/plugins\/ai-engine-pro&quot;,&quot;restUrl&quot;:&quot;https:\/\/111things.com\/wp-json&quot;,&quot;stream&quot;:true,&quot;debugMode&quot;:true,&quot;eventLogs&quot;:false,&quot;speech_recognition&quot;:false,&quot;speech_synthesis&quot;:false,&quot;typewriter&quot;:false,&quot;crossSite&quot;:false,&quot;actions&quot;:[],&quot;blocks&quot;:[],&quot;shortcuts&quot;:[]}' data-theme='{&quot;type&quot;:&quot;internal&quot;,&quot;name&quot;:&quot;Foundation&quot;,&quot;themeId&quot;:&quot;foundation&quot;,&quot;settings&quot;:[],&quot;style&quot;:&quot;&quot;,&quot;cssUrl&quot;:&quot;https:\/\/111things.com\/wp-content\/plugins\/ai-engine-pro\/themes\/foundation.css&quot;}'></div>            </div>

            <div class="get111-quicklinks" aria-label="Quick questions about National Security">
                                                        <button type="button" class="get111-quicklink" data-label="Local Snapshot" data-ask="Give me a quick local snapshot of National Security: what it&#039;s known for, neighborhoods, and vibe.">
                        Local Snapshot                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Housing Snapshot" data-ask="Give me a housing snapshot for National Security: typical rent, home prices, and neighborhood differences.">
                        Housing Snapshot                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Education &amp; Income" data-ask="Summarize education levels, incomes, and major employers in National Security.">
                        Education &amp; Income                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Economy &amp; Work" data-ask="Give me an economy breakdown for National Security: top industries, major employers, and job trends.">
                        Economy &amp; Work                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Growth &amp; Pulse" data-ask="What&#039;s the growth &amp; momentum story in National Security? New development, in-/out-migration, business growth, and what&#039;s changing.">
                        Growth &amp; Pulse                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Health &amp; Lifestyle" data-ask="Summarize health, lifestyle, and what locals do for fun in National Security.">
                        Health &amp; Lifestyle                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Climate &amp; Risk" data-ask="Summarize climate patterns and practical risks in National Security (storms, heat, flooding, etc.).">
                        Climate &amp; Risk                    </button>
                                                        <button type="button" class="get111-quicklink" data-label="Services Mix" data-ask="List common local services people look for in National Security (insurance, finance, legal, home services, etc.).">
                        Services Mix                    </button>
                            </div>
        </div>
        	<item>
		<title>GAO: ODNI has six priority recommendations still open</title>
		<link>https://111things.com/national/gao-odni-has-six-priority-recommendations-still-open/</link>
					<comments>https://111things.com/national/gao-odni-has-six-priority-recommendations-still-open/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Sat, 29 Aug 2026 06:27:17 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[Government Accountability Office]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Office of the Director of National Intelligence]]></category>
		<category><![CDATA[Security Clearances]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=948485</guid>

					<description><![CDATA[A July GAO review says ODNI implemented one priority recommendation but still had six priority and 44 open recommendations, with unreliable clearance data.]]></description>
										<content:encoded><![CDATA[<p>A new Government Accountability Office review says the Office of the Director of National Intelligence implemented only one priority recommendation since <a href="https://www.gao.gov/products/gao-26-107100" rel="nofollow noopener" target="_blank">GAO</a>&#8216;s May 2025 review, leaving six priority recommendations and 44 open recommendations as of June 2026.</p>
<p>GAO published the review on July 14, 2026, and publicly released it on July 21. The update gives Congress a current measure of unresolved oversight work at ODNI and highlights two public risk areas: personnel-vetting weaknesses and intelligence-enterprise management challenges.</p>
<h2>Why the priority count changed</h2>
<p>GAO identified 14 priority recommendations for ODNI in May 2025. By June 2026, the number had fallen to six. ODNI implemented one recommendation, GAO removed priority status from eight others and GAO added one new priority recommendation.</p>
<p>That change does not mean that most of the underlying oversight concerns were resolved. Priority recommendations are a subset of GAO&#8217;s open recommendations. They are recommendations the watchdog believes deserve focused attention because implementation could improve major government operations, reduce mismanagement or address high-risk or duplication concerns.</p>
<p>ODNI had 44 open GAO recommendations overall as of June 2026. Its implementation rate was 48%, while GAO reported a 77% government-wide implementation rate for recommendations made five years earlier. Those figures provide context but are not an apples-to-apples agency ranking: they cover different measurement settings and comparison groups.</p>
<h2>Clearance oversight depends on unreliable data</h2>
<p>The clearest public concern involves the federal personnel security-clearance process. ODNI oversees the process across the government, including efforts to measure how agencies conduct investigations and how long it takes to grant clearances.</p>
<p>GAO said more than 60% of the selected fiscal-year 2024 data it reviewed for ODNI&#8217;s clearance oversight was inaccurate or incomplete. The review covered data across eight reporting requirements and seven selected agencies. The finding applies to the sample GAO examined, not necessarily to every clearance record nationwide.</p>
<p>A separate GAO review, published in December 2025, found that 86% of the timeliness data it analyzed was inaccurate. GAO said most of those errors resulted from a calculation method that did not follow ODNI guidance, and that the problem affected the timeliness measurement for 95% of clearances completed across the government. Much of the data reported to Congress and the public from 2020 through 2024 underestimated the time needed to complete the process.</p>
<p>That matters because inaccurate records can make delays appear shorter or more consistent than they are. It can complicate workforce planning, make it harder to evaluate whether clearance reciprocity is working between agencies and leave Congress without a dependable way to judge whether reforms are producing results.</p>
<h2>What remains outside the public record</h2>
<p>GAO&#8217;s second highlighted risk area is intelligence-enterprise management. Four of the six remaining priority recommendations in that area are sensitive or classified. The public report describes them only broadly, including issues involving business functions, systems and counterterrorism, and does not disclose their substance.</p>
<p>GAO&#8217;s public findings should not be read as allegations of criminal conduct, a security breach or a confirmed intelligence failure. They describe unresolved recommendations and weaknesses in oversight systems and data quality.</p>
<h2>What Congress and ODNI can do next</h2>
<p>GAO says Congress can use hearings, legislation, appropriations and other oversight tools to encourage agencies to address priority recommendations and monitor progress. The watchdog also recommends that ODNI improve the reliability of the information it uses to oversee the clearance process.</p>
<p>ODNI&#8217;s accountability resources include information about transparency, Freedom of Information Act requests and the intelligence community inspector general. Those channels may provide public information about future follow-up, although classified material will remain unavailable to the public.</p>
<h2>What to watch</h2>
<p>The next meaningful signals will be GAO recommendation-status updates, ODNI actions on clearance-data reliability, fiscal-year 2025 and later reporting, and any congressional hearings or legislation focused on the backlog.</p>
<p>The central issue is not a newly announced clearance suspension or breach. It is whether ODNI and Congress have reliable information to oversee a system that affects federal employees and contractors who need access to classified information.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.gao.gov/products/gao-26-107100" rel="nofollow noopener" target="_blank">GAO: Personnel Security Clearances data-reliability review</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/gao-odni-has-six-priority-recommendations-still-open/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">948485</post-id>	</item>
		<item>
		<title>U.S. Seizes China-Linked Hacking Platforms Targeting Critical Infrastructure</title>
		<link>https://111things.com/national/u-s-seizes-china-linked-hacking-platforms-targeting-critical-infrastructure/</link>
					<comments>https://111things.com/national/u-s-seizes-china-linked-hacking-platforms-targeting-critical-infrastructure/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Fri, 28 Aug 2026 23:57:22 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[China]]></category>
		<category><![CDATA[critical infrastructure]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[FBI]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=948355</guid>

					<description><![CDATA[Federal authorities seized three domains tied to QScan and QTRouter after attributing the platforms to a China-linked group targeting U.S. networks.]]></description>
										<content:encoded><![CDATA[<p>The <a href="https://www.justice.gov/opa/pr/justice-department-and-fbi-seize-platforms-operated-and-used-china-state-sponsored-hackers" rel="nofollow noopener" target="_blank">Justice</a> Department and FBI said Wednesday, August 26, 2026, that they seized three domains used by a China-linked hacking group to run scanning and routing platforms that targeted U.S. critical infrastructure and other sensitive networks.</p>
<p>Federal officials said the court-authorized action made the platforms, known as QScan and QTRouter, inoperable because the seized domains were hard-coded into the systems for communication and authentication. The Justice Department updated its announcement on Friday, August 28.</p>
<h2>What the seizure disrupted</h2>
<p>U.S. authorities attribute the platforms to QTFY, which federal records associate with Nanjing Xinjiuwei Network Technology Company. The Justice Department and FBI say the company provided hacking services to paying customers that allegedly included users linked to China’s Ministry of State Security and People’s Liberation Army.</p>
<p>Those descriptions come from a federal affidavit and cybersecurity advisory. They are allegations and investigative assessments, not adjudicated findings.</p>
<p>According to the joint advisory issued by the FBI, National Security Agency and Cyber National Mission Force, QScan was used to scan for vulnerable internet-connected devices and victim networks and to support exploitation activity. QTRouter used compromised internet-of-things devices, commercial proxy devices and leased virtual private servers to obscure the origin and route of attack traffic.</p>
<p>The seizure disrupted the specific command, scanning and routing infrastructure tied to the three domains. It did not establish that every device previously compromised by QTFY had been removed from the group’s control, or that the broader China-linked threat had ended.</p>
<h2>Agencies and sectors identified in federal records</h2>
<p>Federal records name or describe targeting involving NASA, the Federal Reserve, the Departments of Energy, Justice and Health and Human Services, the National Institutes of Health and the U.S. Senate. The records also identify defense contractors, financial institutions, universities, telecommunications companies, hospitals, state and local governments, water systems and election-related networks.</p>
<p>The advisory separates vulnerability scanning, attempted access, successful exploitation and confirmed data theft. Some activity succeeded, including the exfiltration of data from more than 300 organizations in 2024. Other activity was unsuccessful, including scans or attempted intrusions involving the Senate, a hospital system and election-related networks, according to the federal assessment.</p>
<p>That distinction matters: being scanned or targeted does not by itself establish that an organization was breached.</p>
<h2>A threat documented over years</h2>
<p>The joint advisory traces QTFY-related activity to at least 2018. It lists exploitation of vulnerabilities affecting products including Pulse Secure, Citrix, Microsoft Exchange, Log4j, Atlassian Confluence, Check Point, Ivanti, CrushFTP and BeyondTrust.</p>
<p>The timeline includes unsuccessful scanning or access attempts involving U.S. government, health care, power, Senate and election-related networks, as well as successful exploitation and data theft affecting other organizations. Because the activity spans multiple years and product categories, organizations may need to examine older records rather than rely only on current alerts.</p>
<h2>What security teams should do</h2>
<p>The FBI has released QTFY indicators-of-compromise files for defensive review. Security teams should compare the official indicators against historical DNS, proxy, firewall and NetFlow records and preserve relevant logs if a match appears.</p>
<p>Organizations should confirm that internet-facing applications, routers, IoT devices, VPNs, remote-support tools and security appliances have current software and firmware. Federal guidance also recommends protecting operational information exposed through internet-facing services and isolating critical systems from edge devices wherever feasible.</p>
<p>If an organization finds relevant indicators, incident responders should determine whether the activity involved only scanning or progressed to access, persistence or data exfiltration. The advisory directs organizations to contact the FBI’s Internet Crime Complaint Center or a local FBI field office when reporting suspicious or criminal activity, while preserving available evidence and incident details.</p>
<h2>What remains unresolved</h2>
<p>The court-authorized seizure disabled the specific platforms tied to the three domains, but it does not resolve questions about historical compromises, remaining infected devices or replacement infrastructure. It also does not mean that every organization named in federal records was breached.</p>
<p>The advisory’s recommendations are aimed primarily at government agencies, critical-infrastructure operators and security teams. For most consumers, the practical significance is indirect: services that depend on affected organizations may face cyber risk, but the federal action does not identify a general consumer breach or require routine household action.</p>
<p>Next steps to watch include updated technical guidance, victim notifications, further domain seizures, criminal charges or additional findings about how QTFY customers used the infrastructure.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.justice.gov/opa/pr/justice-department-and-fbi-seize-platforms-operated-and-used-china-state-sponsored-hackers" rel="nofollow noopener" target="_blank">U.S. Department of Justice seizure announcement, updated August 28, 2026</a></li>
<li><a href="https://www.ic3.gov/CSA/2026/260826.pdf" rel="nofollow noopener" target="_blank">FBI-NSA-Cyber National Mission Force joint QTFY cybersecurity advisory</a></li>
<li><a href="https://www.reuters.com/world/us/us-says-chinese-hackers-broke-justice-department-nasa-federal-reserve-senate-2026-08-26/" rel="nofollow noopener" target="_blank">Reuters report on the U.S. seizure and named targets</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/u-s-seizes-china-linked-hacking-platforms-targeting-critical-infrastructure/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">948355</post-id>	</item>
		<item>
		<title>Former DIA employee pleads guilty in classified-information case</title>
		<link>https://111things.com/national/former-dia-employee-pleads-guilty-in-classified-information-case/</link>
					<comments>https://111things.com/national/former-dia-employee-pleads-guilty-in-classified-information-case/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Fri, 28 Aug 2026 14:02:39 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Classified information]]></category>
		<category><![CDATA[FBI]]></category>
		<category><![CDATA[Federal Courts]]></category>
		<category><![CDATA[Federal Investigations]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=948104</guid>

					<description><![CDATA[Nathan Laatsch admitted transmitting national defense information during an FBI undercover operation; sentencing is set for January 27, 2027.]]></description>
										<content:encoded><![CDATA[<p>Nathan Vilas Laatsch, a former Defense Intelligence Agency IT specialist, pleaded guilty on August 26, 2026, to transmitting national defense information to a foreign government, the <a href="https://www.justice.gov/opa/pr/former-us-government-employee-pleads-guilty-attempting-provide-classified-information" rel="nofollow noopener" target="_blank">Justice</a> Department announced August 27.</p>
<p>Laatsch, 29, worked with the DIA’s Insider Threat Division and held a Top Secret security clearance. The case shows how an FBI counterintelligence investigation used an undercover contact to document an alleged insider threat before a second handoff led to his arrest.</p>
<h2>How the FBI investigation unfolded</h2>
<p>According to court documents described by federal prosecutors, the FBI learned in March 2025 that Laatsch had offered to provide classified information to what he believed was a friendly foreign government. He then communicated with a person he thought represented that government. The person was actually an undercover FBI agent.</p>
<p>In late April 2025, Laatsch transcribed classified information while working at his desk and removed it from his workspace over approximately three days. He placed the material on a thumb drive and left it at a public park in northern Virginia for the supposed foreign-government representative to retrieve. The FBI recovered the drive, which contained multiple typed documents marked up to the Secret or Top Secret levels.</p>
<p>The public federal announcements do not identify the foreign government. They say Laatsch later expressed interest in obtaining citizenship in that country. The publicly described operation should not be characterized as a completed transfer of U.S. intelligence to a foreign government.</p>
<h2>Arrest followed a second attempted handoff</h2>
<p>After the first drop, the undercover agent told Laatsch that additional classified material could be received. Between May 15 and May 27, 2025, prosecutors said, Laatsch again copied information from a classified workstation and removed it from the facility.</p>
<p>On May 29, 2025, he arrived at a prearranged location in northern Virginia and again transmitted multiple classified documents. He was arrested when the FBI received the materials. That arrest is background to the current development: the new action is Laatsch’s guilty plea, not a new charge or arrest.</p>
<h2>What the guilty plea changes</h2>
<p>By pleading guilty, Laatsch admitted responsibility for the federal offense of transmitting national defense information. The plea resolves the question of guilt in the case, but it does not determine his punishment.</p>
<p>The FBI Washington Field Office investigated the case, with assistance from the bureau’s Global Counterespionage Unit and the Air Force Office of Special Investigations. The DIA cooperated with investigators, according to the Justice Department.</p>
<p>Laatsch’s former assignment in an insider-threat unit is a notable feature of the case. It does not establish that cleared federal employees generally pose a heightened risk. It explains why federal officials have emphasized the contrast between his former responsibilities and the conduct described in the plea-related records.</p>
<h2>Sentencing is scheduled for January 27, 2027</h2>
<p>Laatsch is scheduled to be sentenced on January 27, 2027, in federal court in Alexandria, Virginia. The offense carries a statutory maximum of life in prison, but that maximum is not a prediction of the sentence he will receive.</p>
<p>The sentencing judge will consider the federal sentencing guidelines and other statutory factors before imposing a penalty. Further court filings may provide additional detail about the plea and the government’s sentencing position.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.justice.gov/opa/pr/former-us-government-employee-pleads-guilty-attempting-provide-classified-information" rel="nofollow noopener" target="_blank">U.S. Department of Justice guilty-plea announcement</a></li>
<li><a href="https://www.washingtonpost.com/national-security/2026/08/26/ex-dod-worker-admits-trying-trade-classified-info-foreign-citizenship/" rel="nofollow noopener" target="_blank">The Washington Post</a></li>
<li><a href="https://apnews.com/article/e60388df7f4e07a8d8d942d86513b27c" rel="nofollow noopener" target="_blank">Associated Press</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/former-dia-employee-pleads-guilty-in-classified-information-case/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">948104</post-id>	</item>
		<item>
		<title>GAO Finds Defense Officials Hesitate to Use Some Commercial Space Data</title>
		<link>https://111things.com/national/gao-finds-defense-officials-hesitate-to-use-some-commercial-space-data/</link>
					<comments>https://111things.com/national/gao-finds-defense-officials-hesitate-to-use-some-commercial-space-data/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Fri, 28 Aug 2026 00:32:22 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Commercial Space]]></category>
		<category><![CDATA[Department of Defense]]></category>
		<category><![CDATA[Government Accountability]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Space Force]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=947799</guid>

					<description><![CDATA[A new GAO report says licensing costs, perceived restrictions and unclear access procedures are keeping some Defense officials from using commercial space data.]]></description>
										<content:encoded><![CDATA[<p>Some Defense Department officials are hesitating to purchase or use commercial space data because of licensing costs, perceived restrictions and uncertainty over long-term access, according to a Government Accountability Office report released August 27, 2026.</p>
<p>The report does not say that the military lacks access to all commercial data it buys or that every purchase goes unused. Instead, it identifies a coordination and procurement problem: some potential users may not know what data the government has already purchased, how they are allowed to use it or where to raise access concerns.</p>
<h2>What Defense is buying</h2>
<p>Commercial space companies provide imagery, analytics and other data collected from private satellites and related systems. The Defense Department uses those products alongside government-owned systems for missions that include space-domain awareness and tactical surveillance, reconnaissance and tracking.</p>
<p>Within the Space Force, the Joint Commercial Operations Cell is the main organization that buys commercial space data and related services. <a href="https://www.gao.gov/products/gao-26-107959" rel="nofollow noopener" target="_blank">GAO</a> said the cell spent $76.8 million through the contractor-operated Global Data Marketplace from January 27, 2023, through September 30, 2025.</p>
<p>GAO also reviewed commercial imagery purchased by the National Reconnaissance Office and commercial analytic products purchased by the National Geospatial-Intelligence Agency during fiscal years 2021 through 2025.</p>
<h2>Why some officials held back</h2>
<p>Space Force officials interviewed by GAO cited licensing costs, perceived restrictions on how data could be used and concerns about continued access over the long term. GAO said those challenges contributed to hesitation among potential users to buy and use commercial data.</p>
<p>Those concerns can matter even after a purchase is made. A government entity may hold a license or subscription without every potential operational user knowing that the data exists or understanding the terms governing access and reuse.</p>
<h2>A communication gap</h2>
<p>GAO found that the Joint Commercial Operations Cell leads an informal, monthly Cross-Government Commercial Data Sharing Working Group. The group is intended to coordinate current and future commercial space-data purchases made by federal organizations and to discuss user needs.</p>
<p>But some Space Force officials who reported barriers to GAO were not participating in the group, and information about it was not widely available. GAO said many of the challenges officials described could have been addressed through discussions at the working group.</p>
<p>The watchdog said better communication could bring more Space Force and other government officials into the discussions, help resolve licensing questions and improve use of data and services already purchased.</p>
<h2>What GAO recommended</h2>
<p>GAO recommended that the Secretary of the Air Force ensure the Space Force develops ways to inform current and potential users about the working group and about how to access and use commercial data and services that government entities have purchased.</p>
<p>The Defense Department agreed with the recommendation and said it plans to increase awareness of the working group and access guidance. GAO lists the recommendation as open, meaning the watchdog has not yet confirmed that the department completed the requested action.</p>
<h2>What to watch next</h2>
<p>The next accountability test is whether the Space Force turns that stated plan into documented procedures. Useful signs would include public or internal information that makes the working group easier to find, clearer instructions for accessing existing purchases and evidence that more operational users are using commercial space data.</p>
<p>The immediate issue is not a new authorization or spending program. It is whether the Defense Department can make the commercial capabilities it already buys easier for authorized users to find, understand and apply to national-security missions.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.gao.gov/products/gao-26-107959" rel="nofollow noopener" target="_blank">GAO report GAO-26-107959</a></li>
<li><a href="https://breakingdefense.com/2026/08/space-force-brings-5-companies-on-board-space-data-network/" rel="nofollow noopener" target="_blank">Breaking Defense: Space Data Network</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/gao-finds-defense-officials-hesitate-to-use-some-commercial-space-data/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">947799</post-id>	</item>
		<item>
		<title>NSA watchdog finds gaps in whistleblower language in agency NDAs</title>
		<link>https://111things.com/national/nsa-watchdog-finds-gaps-in-whistleblower-language-in-agency-ndas/</link>
					<comments>https://111things.com/national/nsa-watchdog-finds-gaps-in-whistleblower-language-in-agency-ndas/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Thu, 27 Aug 2026 18:27:22 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[Federal Oversight]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[NSA]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[whistleblowers]]></category>
		<guid isPermaLink="false">https://111things.com/?p=947655</guid>

					<description><![CDATA[An NSA inspector-general review found four of five agency-developed nondisclosure agreements omitted required whistleblower language. NSA agreed to fix the gaps.]]></description>
										<content:encoded><![CDATA[<p>An evaluation issued by the National Security Agency’s inspector general found that four of five NSA-developed nondisclosure agreements reviewed omitted language preserving legally protected whistleblower disclosures.</p>
<p>The NSA agreed with all three recommendations and said it will create a compliance process, assign responsibility to senior officials and revise existing agency-developed documents. Those are planned corrective actions, not confirmation that every affected form has already been changed.</p>
<h2>What the watchdog found</h2>
<p>The NSA Office of the Inspector General issued the evaluation on August 18, 2026. <a href="https://www.oversight.gov/reports/evaluation-nsas-implementation-whistleblower-protection-provisions-nondisclosure-agreements">Oversight.gov identifies it as an agency-wide inspection and evaluation</a> of the NSA’s implementation of whistleblower protections in nondisclosure policies, forms and agreements.</p>
<p>The review found that NSA did not have an overarching nondisclosure-agreement policy, a defined development process, a central official or office responsible for the documents, or a single repository containing all NSA-developed agreements.</p>
<p>That lack of centralized control also limited the review. The OIG said NSA could not provide a complete list of all agency-developed nondisclosure agreements, so the watchdog could not assure that the documents examined represented the full universe of forms used by the agency.</p>
<h2>Four of five reviewed agreements lacked the protections</h2>
<p>The OIG identified five unique NSA-developed nondisclosure agreements. One Security Agreement did not contain the current required whistleblower provisions, although it included related language and some statutory references.</p>
<p>The other four agreements made no mention of whistleblower protections. The documents included agreements for test proctors, people performing system testing and certifying testing materials, and members of an NSA Advisory Board.</p>
<p>The watchdog also identified five additional agreements that were not titled or identified as nondisclosure agreements but still implied nondisclosure obligations without including the required protections.</p>
<p>Electronic brief sheets used for access to compartmented information presented another gap. Individual offices developed the sheets from a template, and an affiliate’s electronic acknowledgment served as the nondisclosure agreement. The OIG found that the template and the brief sheets it reviewed lacked the required whistleblower language.</p>
<p>The OIG noted that the ODNI Form FM4414, used when a hard-copy agreement is required, does contain the statutory language. The evaluation focused on NSA policy and NSA-developed agreements governing employees; documents developed exclusively for nonemployee affiliates were outside the review’s scope.</p>
<h2>What federal law requires</h2>
<p>Section 743 of Division E of the Consolidated Appropriations Act, 2026, Public Law 119-75, bars the use of appropriated funds to implement or enforce covered nondisclosure policies, forms or agreements that do not contain language preserving legally protected disclosures.</p>
<p>The required provisions address employees’ rights and obligations involving classified information, communications to Congress, reports to inspectors general and other protected whistleblower disclosures involving violations of law, mismanagement, gross waste, abuse of authority or substantial and specific dangers to public health or safety.</p>
<p>The law does not eliminate employees’ duties to protect classified information or authorize the public release of classified material. The OIG also noted that omitting a reference to the Office of Special Counsel alone does not make an agreement noncompliant because the office lacks jurisdiction over counterintelligence and foreign-intelligence disclosures.</p>
<h2>NSA response and next steps</h2>
<p>NSA management agreed with the OIG’s three recommendations. The agency said it would develop and document a process to keep required whistleblower language current, identify the officials responsible for compliance, and find and revise existing NSA-developed nondisclosure policies, forms and agreements.</p>
<p>Under the response, the NSA chief of staff will lead the accountability effort and hold directorate-level chiefs of staff responsible for their areas. The Engagement and Policy Directorate’s Enterprise Guidance Services will help implement the process and revisions.</p>
<p>The evaluation followed an inquiry from Sen. Charles E. Grassley that prompted the OIG’s initial assessment. Fieldwork for the formal evaluation took place from August 2025 through February 2026.</p>
<p>The main follow-up question is whether NSA produces a complete inventory of its nondisclosure documents and confirms that revised agreements, implied-nondisclosure documents and compartmented-access brief sheets include the required protections. The report identifies a document-governance and notice problem, but it does not find that every NSA nondisclosure agreement was deficient or that personnel were intentionally prevented from reporting misconduct.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.oversight.gov/sites/default/files/documents/reports/2026-08/Evaluation%20of%20NSA%27s%20Implementation%20of%20Whistleblower%20Protection%20Provisions%20in%20Nondisclosure%20Agreements.pdf" rel="nofollow noopener" target="_blank">NSA Office of Inspector General evaluation, Aug. 18, 2026</a></li>
<li><a href="https://www.govinfo.gov/content/pkg/PLAW-119publ75/pdf/PLAW-119publ75.pdf" rel="nofollow noopener" target="_blank">Public Law 119-75, Section 743</a></li>
<li><a href="https://federalnewsnetwork.com/federal-newscast/2026/08/nsa-isnt-complying-with-federal-laws-on-whistleblower-protections-ig-finds/" rel="nofollow noopener" target="_blank">Federal News Network, Aug. 25, 2026</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/nsa-watchdog-finds-gaps-in-whistleblower-language-in-agency-ndas/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">947655</post-id>	</item>
		<item>
		<title>Trump Declares Emergency Over Foreign Risks to U.S. Power Grid</title>
		<link>https://111things.com/national/trump-declares-emergency-over-foreign-risks-to-u-s-power-grid/</link>
					<comments>https://111things.com/national/trump-declares-emergency-over-foreign-risks-to-u-s-power-grid/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Thu, 27 Aug 2026 17:32:17 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Disaster Response]]></category>
		<category><![CDATA[Electric grid]]></category>
		<category><![CDATA[Emergency Management]]></category>
		<category><![CDATA[energy]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=947633</guid>

					<description><![CDATA[President Trump’s August 26 order gives Energy officials new authority over some foreign-linked bulk-power equipment, but rules and lists are still pending.]]></description>
										<content:encoded><![CDATA[<p>President Donald Trump declared a national emergency on August 26, 2026, over what the White House described as risks associated with foreign-produced equipment used in the U.S. bulk-power system. Executive Order 14420 gives the Energy Department new authority to review and restrict certain transactions while setting deadlines for future grid-security rules and federal procurement recommendations.</p>
<p>The order does not immediately ban every foreign-made electricity product or direct utilities to remove equipment nationwide. Restrictions generally require the Energy Secretary to make specified risk determinations involving covered foreign entities, equipment or transactions.</p>
<h2>What the order covers</h2>
<p>Executive Order 14420 covers certain foreign-produced equipment used in bulk-power transmission and generation, as well as associated critical components, software, firmware, digital services, maintenance services and remote-access capabilities.</p>
<p>The order identifies risks that may include sabotage, subversion, unauthorized access, malicious remote action, supply disruption, catastrophic effects on critical infrastructure or other unacceptable risks to national security and public safety. These are the administration’s stated concerns; the order does not identify a specific utility, vendor or device as having caused a confirmed compromise.</p>
<p>Once the required determinations are made, the Energy Department may prohibit covered acquisitions, imports, transfers or installations. The department may also issue licenses, require mitigation measures and establish pre-qualified equipment or vendor lists. The structure is therefore a risk-based review system, not an automatic prohibition on all foreign suppliers.</p>
<h2>Transmission and generation are covered; local distribution is excluded</h2>
<p>For purposes of the order, the bulk-power system includes facilities and control systems needed to operate an interconnected electric transmission network, along with generation facilities needed to maintain reliability. The definition includes transmission lines rated at 69 kilovolts or more.</p>
<p>Facilities used in the local distribution of electricity are excluded from the order’s definition. That distinction matters: the order focuses on high-voltage transmission and reliability-related generation assets, not every piece of neighborhood distribution equipment.</p>
<h2>Why the policy matters for disaster response</h2>
<p><a href="https://www.fema.gov/sites/default/files/documents/fema_incident-annex_power-outage.pdf" rel="nofollow noopener" target="_blank">FEMA</a> treats energy as a community lifeline during emergencies. Electricity supports communications, transportation, food distribution, housing, water and wastewater systems, health care and public safety.</p>
<p>FEMA’s power-outage planning assigns the Energy Department a role in coordinating federal energy-restoration support, while FEMA coordinates broader lifesaving and life-sustaining assistance. A major disruption to the bulk-power system could therefore affect emergency communications, hospitals, water systems, fuel distribution and transportation well beyond the immediate outage area.</p>
<p>Those FEMA documents provide emergency-management context; they do not assess whether this executive order will increase or reduce outages. Consumers should not assume an immediate change to household power service based solely on the August 26 declaration.</p>
<h2>Existing equipment could face conditions later</h2>
<p>The order allows the Energy Secretary, after making the required determinations, to impose conditions on foreign-manufactured or foreign-operated bulk-power equipment acquired or installed before August 26. Possible measures include identification, monitoring, securing, isolation, disconnection, replacement or removal.</p>
<p>Before directing isolation, disconnection, replacement or removal, the department must consider reliability, safety, the availability of secure replacements and continuity of essential service. The order also allows phased compliance. It does not itself confirm that any existing equipment will be removed.</p>
<h2>What utilities and contractors may watch</h2>
<p>Utilities, contractors and technology suppliers may need to monitor future guidance on equipment inventories, vendor qualification, maintenance and software updates, remote access, mitigation plans and replacement procedures. The operational and cost effects remain potential consequences until agencies, utilities, vendors or regulators provide more specific estimates.</p>
<p>The order also directs the Energy Department to identify covered equipment and develop recommendations for inventorying, isolating, monitoring or replacing items that officials determine pose unacceptable risks. No complete public list of prohibited products, covered entities or required replacements had been established in the order itself.</p>
<h2>The first deadlines are months away</h2>
<p>The Energy Secretary must publish implementing rules or regulations within 120 days of August 26, 2026. Within 180 days, the secretary must submit recommendations for changes to the Federal Acquisition Regulation to ensure national-security risks are considered in federal energy-infrastructure procurement and to prioritize U.S.-manufactured infrastructure.</p>
<p>Within 90 days after receiving those recommendations, the Federal Acquisition Regulatory Council must consider whether to propose amendments for public comment. The process could therefore extend well beyond the initial 120- and 180-day milestones.</p>
<p>For now, the confirmed change is expanded federal authority and a timetable for implementation. The order does not establish an immediate nationwide shutdown, universal ban, confirmed removal program or automatic change in electricity prices, outage frequency or household utility bills.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.whitehouse.gov/presidential-actions/2026/08/declaring-a-national-emergency-to-secure-the-united-states-bulk-power-system/" rel="nofollow noopener" target="_blank">Executive Order 14420, White House</a></li>
<li><a href="https://www.fema.gov/sites/default/files/documents/fema_incident-annex_power-outage.pdf" rel="nofollow noopener" target="_blank">Power Outage Incident Annex, FEMA</a></li>
<li><a href="https://www.investing.com/news/commodities-news/trump-signs-order-banning-some-foreign-equipment-from-us-energy-grid-4877834" rel="nofollow noopener" target="_blank">Reuters, Trump signs order banning some foreign equipment from U.S. energy grid</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/trump-declares-emergency-over-foreign-risks-to-u-s-power-grid/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">947633</post-id>	</item>
		<item>
		<title>DOJ and FBI Seize 13 Websites Targeting Clearance Holders</title>
		<link>https://111things.com/national/doj-and-fbi-seize-13-websites-targeting-clearance-holders/</link>
					<comments>https://111things.com/national/doj-and-fbi-seize-13-websites-targeting-clearance-holders/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Wed, 12 Aug 2026 14:22:18 +0000</pubDate>
				<category><![CDATA[Crime, Courts & Public Safety]]></category>
		<category><![CDATA[National]]></category>
		<category><![CDATA[counterintelligence]]></category>
		<category><![CDATA[Department of Justice]]></category>
		<category><![CDATA[FBI]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Security Clearances]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/doj-and-fbi-seize-13-websites-targeting-clearance-holders/</guid>

					<description><![CDATA[The Justice Department and FBI seized 13 domains they said were backed by suspected Chinese agents and used fake consulting offers to seek sensitive information from current and former U.S. security-clearance holders.]]></description>
										<content:encoded><![CDATA[<p>The Justice Department and FBI seized 13 internet domains on June 10, 2026, alleging that the websites were backed by suspected Chinese agents and used deceptive consulting opportunities to target current and former U.S. security-clearance holders.</p>
<p>Federal authorities said the sites were used to solicit sensitive U.S. information from people who held or previously held security clearances. The alleged approach presented the contacts as consulting or employment opportunities, according to the Justice Department.</p>
<p>The FBI replaced all 13 seized domains with takeover warning pages. Those pages served as the immediate public response to the websites and alerted visitors that the federal government had intervened.</p>
<h2>What authorities allege</h2>
<p>The Justice Department said the websites offered fake consulting opportunities designed to induce people to disclose classified or otherwise sensitive information. The alleged targets included both current clearance holders and people who no longer held clearances.</p>
<p>Federal authorities described the domains as backed by suspected Chinese agents. That wording identifies the alleged connection described by the department, but it does not establish that Chinese government officials directly operated the websites.</p>
<p>The department also linked the activity to money laundering. The public announcement did not identify individual defendants in connection with the domains, and the seizure was announced as a government action against the websites rather than as a reported conviction or final court finding.</p>
<p>The alleged targeting extended to U.S. persons nationwide. The action therefore involved a national audience even though the investigation specifically included the FBI field offices in Washington and Norfolk.</p>
<h2>Federal response</h2>
<p>The investigation involved the Justice Department’s National Security Division, the FBI Washington Field Office and the FBI Norfolk Field Office. Together, the agencies took control of the 13 internet domains and placed warning pages on them.</p>
<p>The seizure interrupted the websites’ public operation and made the alleged recruiting approach visible to people who might otherwise have encountered the consulting offers. The FBI’s warning pages also distinguished the federal action from a routine website closure: visitors were shown that the domains had been taken over by authorities.</p>
<p>The Justice Department said the sites sought information from people with current or past access to classified or sensitive U.S. government information. That focus is central to the national-security concern described by the department: foreign intelligence services may seek to recruit people who possess specialized knowledge or access through apparently legitimate professional opportunities.</p>
<p>The operation illustrates a counterintelligence effort aimed at preventing the recruitment of people connected to classified or sensitive government work. It also shows how federal authorities can respond publicly to suspected online solicitation by disabling the domains and using the seized websites to warn potential visitors.</p>
<p>The action does not, by itself, establish that a particular person disclosed classified information through the sites. The Justice Department announcement did not report arrests or criminal charges, and it did not say whether anyone provided classified or sensitive information in response to the alleged offers.</p>
<p>For current and former security-clearance holders, the federal action identifies deceptive consulting opportunities as the alleged vehicle used by the 13 domains. The warning pages remain the concrete public measure described in the announcement, while the investigation continues through the Justice Department’s National Security Division and the FBI offices in Washington and Norfolk.</p>
<p><!-- esn-ng-sources:start --></p>
<section class="esn-ng-source-section">
<h2>Sources</h2>
<ul class="esn-ng-sources">
<li><a href="https://www.justice.gov/opa/pr/justice-department-fbi-disable-13-websites-backed-suspected-chinese-agents-sought-sensitive">Justice Department, FBI Disable 13 Websites Backed by Suspected Chinese Agents That Sought Sensitive U.S. Information from Security Clearance Holders</a><span class="esn-ng-source-organization">, U.S. Department of Justice</span></li>
</ul>
</section>
<p><!-- esn-ng-sources:end --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/doj-and-fbi-seize-13-websites-targeting-clearance-holders/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">946817</post-id>	</item>
		<item>
		<title>White House orders tighter domestic sourcing and supply-chain mapping for defense materials</title>
		<link>https://111things.com/national/white-house-orders-tighter-domestic-sourcing-and-supply-chain-mapping-for-defense-materials/</link>
					<comments>https://111things.com/national/white-house-orders-tighter-domestic-sourcing-and-supply-chain-mapping-for-defense-materials/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 17:37:19 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Politics & Government]]></category>
		<category><![CDATA[Critical Materials]]></category>
		<category><![CDATA[Defense contractors]]></category>
		<category><![CDATA[Defense supply chains]]></category>
		<category><![CDATA[Donald Trump]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[U.S. Department of Defense]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/white-house-orders-tighter-domestic-sourcing-and-supply-chain-mapping-for-defense-materials/</guid>

					<description><![CDATA[Executive Order 14415 directs the Pentagon and defense contractors to favor domestic or allied sources, map critical supply chains and limit certain waivers beginning Jan. 1, 2027.]]></description>
										<content:encoded><![CDATA[<p>President Donald Trump signed an executive order July 20 directing the Defense Department and the military departments to strengthen domestic and allied sourcing of critical defense materials while requiring defense contractors to map those supply chains from raw materials through finished products.</p>
<p>Executive Order 14415 is aimed at reducing vulnerabilities in the materials and supplier networks used to manufacture, maintain and repair military equipment. The order frames those vulnerabilities as potential targets for physical, cyber and economic subversion.</p>
<p>The directive applies across the Defense Department and to prime contractors and subcontractors supporting U.S. national security. It does not itself identify every material, contract or supplier that will be affected. Those details are to be addressed through policy and implementation work.</p>
<h2>What the order directs</h2>
<p>The order says covered critical defense materials should be sourced domestically or from allied nations. It directs the secretary of Defense to develop policy and implementation guidance within 180 days.</p>
<p>That guidance is expected to establish how the sourcing policy will operate across the department and its military departments. The order also directs prime contractors and subcontractors at every tier to “map and illuminate” covered critical supply chains, tracing them from raw materials through end-use products.</p>
<p>Supply-chain mapping is intended to give the government greater visibility into the companies, materials and stages involved in defense production. The order does not state that domestic production has already increased or that any specific weapons program or contractor has lost access to materials.</p>
<p>Beginning Jan. 1, 2027, the military departments are directed to stop issuing waivers under 10 U.S.C. 4872(c)(1), subject to exceptions specified in the order. The provision concerns restrictions tied to the acquisition of certain materials for the Defense Department.</p>
<h2>Reporting and implementation</h2>
<p>The administration must submit implementation reports every six months through Jan. 1, 2028. Those reports are intended to describe progress in putting the order into effect.</p>
<p>The timeline creates several milestones. The first major deadline is the 180-day period for Defense Department policy and implementation guidance. The waiver restriction begins later, on Jan. 1, 2027, while the recurring reports extend into 2028.</p>
<p>The practical cost and timeline for contractor compliance have not been specified. Contractors and subcontractors will need to account for requirements that are developed through the department’s guidance, but the order itself does not set out a complete list of affected suppliers, materials or contracts.</p>
<h2>Broader security concerns</h2>
<p>The order’s focus on visibility reflects a broader concern that weaknesses in defense supply chains can affect national security even when a final weapons system remains available. A disruption, hidden dependency or compromised supplier can create problems earlier in the production and maintenance process.</p>
<p>A January 2026 Government Accountability Office report identified funding, staffing, training and operational challenges in the Defense Counterintelligence and Security Agency’s industrial-security mission. The GAO also said that, as of January 2026, some related policy changes had not been coordinated across the Defense Department.</p>
<p>Those findings provide context for the administration’s emphasis on implementation and oversight. The executive order assigns new policy, mapping and reporting tasks, but the eventual effect will depend on the guidance issued by the Defense Department and how contractors carry out the requirements.</p>
<p>For now, Executive Order 14415 establishes the direction of policy rather than documenting a completed procurement change. Its next identified steps are the Defense Department’s guidance within 180 days, the Jan. 1, 2027 waiver deadline with stated exceptions, and the six-month implementation reports continuing through Jan. 1, 2028.</p>
<p><!-- esn-ng-sources:start --></p>
<section class="esn-ng-source-section">
<h2>Sources</h2>
<ul class="esn-ng-sources">
<li><a href="https://www.whitehouse.gov/presidential-actions/2026/07/securing-americas-defense-supply-chains-and-ensuring-domestic-acquisition-of-critical-materials/?cst=&amp;query-11-page=63">Securing America&#039;s Defense Supply Chains and Ensuring Domestic Acquisition of Critical Materials</a><span class="esn-ng-source-organization">, The White House</span></li>
<li><a href="https://files.gao.gov/reports/GAO-26-107861/index.html">Industrial Security: Improved Risk Management and Stakeholder Engagement Needed to Help DOD Address Mission Gaps</a><span class="esn-ng-source-organization">, U.S. Government Accountability Office</span></li>
</ul>
</section>
<p><!-- esn-ng-sources:end --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/white-house-orders-tighter-domestic-sourcing-and-supply-chain-mapping-for-defense-materials/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">946360</post-id>	</item>
		<item>
		<title>FCC moves to block imports and marketing of some previously authorized communications equipment</title>
		<link>https://111things.com/national/fcc-moves-to-block-imports-and-marketing-of-some-previously-authorized-communications-equipment/</link>
					<comments>https://111things.com/national/fcc-moves-to-block-imports-and-marketing-of-some-previously-authorized-communications-equipment/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 11:07:20 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Politics & Government]]></category>
		<category><![CDATA[communications equipment]]></category>
		<category><![CDATA[Covered List]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Federal Communications Commission]]></category>
		<category><![CDATA[Kaspersky Lab]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/fcc-moves-to-block-imports-and-marketing-of-some-previously-authorized-communications-equipment/</guid>

					<description><![CDATA[A Federal Communications Commission notice says continued importation and marketing of certain Covered List equipment, including equipment with integrated Kaspersky cybersecurity or antivirus software, should be prohibited because of national-security risks.]]></description>
										<content:encoded><![CDATA[<p>The Federal Communications Commission is moving to prohibit the continued importation and marketing of certain communications equipment that had previously been authorized, saying the action is necessary to address national-security risks.</p>
<p>In a notice released June 26, 2026, the FCC concluded that some equipment already placed on the agency’s Covered List should no longer be brought into or marketed in the United States. The notice specifically discusses equipment with integrated Kaspersky Lab cybersecurity or antivirus software.</p>
<p>The action places the FCC’s communications-equipment approval system at the center of a broader national-security effort. Equipment on the Covered List is considered by the federal government to pose an unacceptable risk to U.S. national security or to the security and safety of people in the United States.</p>
<h2>What the notice says</h2>
<p>The document, identified as DA 26-635, was issued by the FCC’s Public Safety and Homeland Security Bureau and Office of Engineering and Technology. It says continued importation and marketing of certain previously authorized Covered List equipment should be prohibited.</p>
<p>That wording is significant because the equipment addressed by the notice had already received authorization at an earlier point. The FCC’s action concerns whether that equipment should continue entering the U.S. market or being marketed after national-security determinations placed it within the Covered List framework.</p>
<p>The notice links the decision to risks involving the United States, U.S. communications networks and U.S. persons. Its discussion of equipment with integrated Kaspersky Lab cybersecurity or antivirus software makes the company’s technology a specific part of the agency’s latest action.</p>
<p>The notice does not describe a prohibition on all Kaspersky software or all foreign telecommunications equipment. Its stated focus is certain communications equipment already covered by the FCC’s national-security framework.</p>
<h2>Why it matters</h2>
<p>Communications equipment can become part of the infrastructure used to connect people, organizations and networks. A decision to restrict the importation or marketing of equipment therefore affects more than a product’s regulatory status: It can narrow the equipment available to the U.S. communications market and reflects federal concern about the security of network infrastructure.</p>
<p>The FCC’s action also shows how national-security determinations can continue to affect equipment that was previously authorized. The agency is not treating earlier authorization as permanently settling whether the equipment can remain available in the U.S. market.</p>
<p>For businesses and other organizations that buy communications equipment, the practical significance will depend on which products are covered and how the restriction is implemented. The notice discusses the policy conclusion but does not identify every affected model or provide a complete implementation timetable.</p>
<p>The public notice also does not, by itself, establish that equipment already deployed must be removed. The action described is directed at continued importation and marketing, and any separate requirements affecting existing inventories or installed equipment would depend on the applicable FCC order and notices to affected parties.</p>
<h2>What happens next</h2>
<p>The June 26 notice follows earlier FCC proceedings and national-security determinations concerning equipment on the Covered List. Those earlier steps provide the basis for the agency’s conclusion that continued market access for the specified equipment should be prohibited.</p>
<p>The next practical questions are which models and configurations fall within the restriction, when the change takes effect and how affected companies must handle inventory and future sales. The FCC notice does not set out all of those details in the document released June 26.</p>
<p>What it does establish is the agency’s position: For the covered equipment addressed in the notice, continued importation and marketing is considered inconsistent with protecting U.S. national security and the security and safety of U.S. persons.</p>
<p><!-- esn-ng-sources:start --></p>
<section class="esn-ng-source-section">
<h2>Sources</h2>
<ul class="esn-ng-sources">
<li><a href="https://docs.fcc.gov/public/attachments/DA-26-635A1.pdf">DA 26-635: Public Safety notice on Covered List equipment</a><span class="esn-ng-source-organization">, Federal Communications Commission</span></li>
</ul>
</section>
<p><!-- esn-ng-sources:end --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/fcc-moves-to-block-imports-and-marketing-of-some-previously-authorized-communications-equipment/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">946210</post-id>	</item>
		<item>
		<title>GAO: Defense Security Agency Completes Fewer Than 40% of Required Contractor Inspections</title>
		<link>https://111things.com/national/gao-defense-security-agency-completes-fewer-than-40-of-required-contractor-inspections/</link>
					<comments>https://111things.com/national/gao-defense-security-agency-completes-fewer-than-40-of-required-contractor-inspections/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Tue, 11 Aug 2026 02:57:19 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Politics & Government]]></category>
		<category><![CDATA[Classified information]]></category>
		<category><![CDATA[Defense contractor security]]></category>
		<category><![CDATA[Defense Department]]></category>
		<category><![CDATA[Government Accountability Office]]></category>
		<category><![CDATA[inspections]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/gao-defense-security-agency-completes-fewer-than-40-of-required-contractor-inspections/</guid>

					<description><![CDATA[A Government Accountability Office review found that the Defense Counterintelligence and Security Agency completes less than 40% of required inspections at contractor facilities handling classified information. The report cites workforce and information-technology weaknesses and says its recommendations remain open.]]></description>
										<content:encoded><![CDATA[<p>The Defense Counterintelligence and Security Agency completes less than 40% of the inspections it is required to conduct at contractor facilities handling classified information, according to a new Government Accountability Office review.</p>
<p>GAO released the 63-page report, GAO-26-107861, on April 24, 2026. The review identified workforce limitations and an inadequate information-technology system at DCSA, the Defense Department agency responsible for helping protect classified information held by defense contractors.</p>
<p>The finding points to a substantial gap between the inspections required under the national industrial-security program and the inspections completed. Those inspections are intended to help the government assess whether facilities handling classified information are meeting security requirements.</p>
<h2>Workforce and technology gaps</h2>
<p>GAO said DCSA’s ability to carry out its inspection responsibilities is limited by staffing problems and weaknesses in its information-technology system. The agency’s current system lacks analytic capabilities needed to identify risks and regional trends more effectively.</p>
<p>That limitation affects more than recordkeeping. Without stronger analysis, DCSA has less ability to determine where security risks may be concentrated, compare conditions across regions and direct limited inspection resources toward the facilities or issues requiring the most attention.</p>
<p>The inspection shortfall is a documented oversight concern for the national-security information held by defense contractors. The report does not establish that the gap caused a specific classified-information breach, and it does not identify a particular contractor facility as having been compromised.</p>
<p>The public report also does not provide a current estimate of how many contractor facilities went uninspected. Its central finding is instead expressed as a share of the inspections DCSA was required to complete: less than 40%.</p>
<h2>Recommendations remain open</h2>
<p>GAO issued recommendations aimed at improving how DCSA responds to security risks, sets performance goals, aligns its organization and engages with stakeholders. The recommendations remained open pending documented agency action.</p>
<p>The recommendations address both the agency’s immediate inspection work and the management systems used to oversee that work. Clearer performance goals could make it easier to measure whether DCSA is closing the gap between required and completed inspections. Better organizational alignment could clarify responsibilities, while stronger stakeholder engagement could improve coordination with the contractors and other participants in the security program.</p>
<p>GAO also linked the agency’s mission gaps to risk management. The report’s title calls for improved risk management and stakeholder engagement to help the Defense Department address those gaps, underscoring that the issue is not limited to the number of inspections performed.</p>
<h2>Why the finding matters</h2>
<p>Defense contractors are part of the National Industrial Security Program, which governs the protection of classified information in the private sector. DCSA’s inspection role gives the Defense Department a way to evaluate security practices at facilities that support national-defense work.</p>
<p>A completion rate below 40% means that most of the required inspections were not completed during the period covered by GAO’s review. That does not by itself show that classified information was lost or exposed, but it does show that the government’s planned oversight did not occur at the level required.</p>
<p>The result also places greater importance on the agency’s ability to prioritize. GAO’s concerns about analytics, staffing and performance goals suggest that DCSA’s response will involve not only conducting more inspections, but also improving how it identifies risk and measures progress.</p>
<p>The next known step is documented action by the Defense Department and DCSA on GAO’s open recommendations. The April 24 report does not announce a new inspection deadline. Until the recommendations are addressed and closed, GAO’s findings remain an unresolved oversight issue for the federal program responsible for protecting classified information held by defense contractors.</p>
<p><!-- esn-ng-sources:start --></p>
<section class="esn-ng-source-section">
<h2>Sources</h2>
<ul class="esn-ng-sources">
<li><a href="https://www.gao.gov/products/gao-26-107861">Industrial Security: Improved Risk Management and Stakeholder Engagement Needed to Help DOD Address Mission Gaps</a><span class="esn-ng-source-organization">, U.S. Government Accountability Office</span></li>
<li><a href="https://www.oversight.gov/reports/report-presidents-surveillance-program-unclassified-prepared-offices-inspectors-general-3">Report on the President’s Surveillance Program — Recommendation 4</a><span class="esn-ng-source-organization">, Council of the Inspectors General on Integrity and Efficiency</span></li>
</ul>
</section>
<p><!-- esn-ng-sources:end --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/gao-defense-security-agency-completes-fewer-than-40-of-required-contractor-inspections/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">946018</post-id>	</item>
		<item>
		<title>FCC Moves to Bar Marketing of Certain Communications Equipment Tied to Kaspersky</title>
		<link>https://111things.com/national/fcc-moves-to-bar-marketing-of-certain-communications-equipment-tied-to-kaspersky/</link>
					<comments>https://111things.com/national/fcc-moves-to-bar-marketing-of-certain-communications-equipment-tied-to-kaspersky/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Mon, 10 Aug 2026 21:32:36 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Science & Technology]]></category>
		<category><![CDATA[communications equipment]]></category>
		<category><![CDATA[Covered List]]></category>
		<category><![CDATA[Federal Communications Commission]]></category>
		<category><![CDATA[Kaspersky Lab]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Supply Chain Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/fcc-moves-to-bar-marketing-of-certain-communications-equipment-tied-to-kaspersky/</guid>

					<description><![CDATA[The FCC adopted an action addressing the continued importation and marketing of previously authorized communications equipment on the agency’s Covered List, including equipment with integrated Kaspersky cybersecurity or antivirus products.]]></description>
										<content:encoded><![CDATA[<p>The Federal Communications Commission has moved to bar the continued importation and marketing of certain communications equipment that had previously been authorized but was later placed on the agency’s Covered List, citing risks to national security and public safety.</p>
<p>The FCC issued the action, DA 26-635, on June 26, 2026. It addresses equipment added to the Covered List in 2024 or earlier and focuses on whether products that had already received authorization should continue to enter the United States market.</p>
<p>The action specifically discusses equipment incorporating cybersecurity or antivirus products from Kaspersky Lab. The FCC said equipment containing those products presents an unacceptable risk to U.S. national security or to the security and safety of people in the United States.</p>
<h2>What the FCC action covers</h2>
<p>The Covered List is part of the FCC’s framework for identifying communications equipment and services that raise national-security or public-safety concerns. DA 26-635 addresses a category of equipment that was previously authorized but later added to that list.</p>
<p>That distinction matters. The action is not described as a blanket order declaring that every device associated with Kaspersky is immediately disabled or removed from service. Instead, it concerns continued importation and marketing of specified equipment that had already received authorization before being added to the Covered List.</p>
<p>The practical question is whether companies can continue bringing the affected equipment into the United States or promoting it for use in communications networks. The FCC’s stated concern is that allowing such products to remain in the supply chain could expose U.S. communications infrastructure or users to unacceptable security risks.</p>
<p>The FCC action identifies the broad category of equipment involved, but it does not provide a complete public inventory of every affected model or establish the number of U.S. devices or networks that could be involved. Those details are important for manufacturers, distributors, network operators and customers trying to determine whether a particular product is covered.</p>
<h2>Why the agency says it matters</h2>
<p>The decision is part of broader FCC efforts focused on communications-network cybersecurity and supply-chain security. Those efforts address the risk that vulnerabilities in hardware, software or equipment suppliers could affect services that depend on reliable communications.</p>
<p>A separate FCC communications on cybersecurity risks to next-generation 911 and communications networks describes how software failures and cybersecurity incidents can contribute to outages across multiple states. It also points to mitigation measures such as network monitoring, vulnerability assessments, backup systems and response plans.</p>
<p>Those recommendations provide context for the FCC’s concern with equipment used in communications systems. A security problem involving a product or supplier can have consequences beyond an individual device if the equipment is integrated into a larger network. For emergency communications and other critical services, disruptions can affect the ability of people and organizations to connect when reliability is essential.</p>
<p>The agency’s action therefore reaches beyond a product-labeling issue. It reflects a policy judgment that some equipment already authorized for the U.S. market should not continue to be imported or marketed after being identified as presenting national-security concerns.</p>
<h2>What happens next</h2>
<p>DA 26-635 establishes the FCC’s action on the continued importation and marketing of the covered equipment. Companies that manufacture, distribute or deploy communications equipment will need to determine how the action applies to their products and supply chains.</p>
<p>The public action does not, by itself, provide a complete list of affected models, the number of deployed devices or every compliance date. It also does not establish that all Kaspersky-related equipment has been taken out of service. The immediate significance is the FCC’s decision to address continued market access for equipment that had been authorized before appearing on the Covered List.</p>
<p>For network operators and public-safety authorities, the broader FCC cybersecurity guidance emphasizes preparedness: monitoring systems, assessing vulnerabilities, maintaining backups and having response plans. Those steps are presented as ways to reduce the effects of software failures, cyber incidents and other disruptions affecting communications networks.</p>
<p>The FCC’s action places supply-chain security and the treatment of previously authorized equipment at the center of that work. Its stated goal is to prevent communications products the agency considers an unacceptable national-security or public-safety risk from continuing to enter or circulate in the U.S. market.</p>
<p><!-- esn-ng-sources:start --></p>
<section class="esn-ng-source-section">
<h2>Sources</h2>
<ul class="esn-ng-sources">
<li><a href="https://docs.fcc.gov/public/attachments/DA-26-635A1.pdf">DA 26-635</a><span class="esn-ng-source-organization">, Federal Communications Commission</span></li>
<li><a href="https://docs.fcc.gov/public/attachments/DOC-422169A1.pdf">FCC-IRC2606-03</a><span class="esn-ng-source-organization">, Federal Communications Commission</span></li>
</ul>
</section>
<p><!-- esn-ng-sources:end --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/fcc-moves-to-bar-marketing-of-certain-communications-equipment-tied-to-kaspersky/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">945894</post-id>	</item>
		<item>
		<title>House passes defense bill backing $1.15 trillion national-security package and Department of War renaming</title>
		<link>https://111things.com/national/house-passes-defense-bill-backing-1-15-trillion-national-security-package-and-department-of-war-renaming/</link>
					<comments>https://111things.com/national/house-passes-defense-bill-backing-1-15-trillion-national-security-package-and-department-of-war-renaming/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Fri, 07 Aug 2026 16:32:07 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Politics & Government]]></category>
		<category><![CDATA[Defense spending]]></category>
		<category><![CDATA[Department of Defense]]></category>
		<category><![CDATA[Department of War]]></category>
		<category><![CDATA[military pay]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[U.S. House of Representatives]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/house-passes-defense-bill-backing-1-15-trillion-national-security-package-and-department-of-war-renaming/</guid>

					<description><![CDATA[The House passed a defense-policy bill on July 22, 2026, that incorporates President Donald Trump’s $1.15 trillion national-security spending request and proposes renaming the Department of Defense.]]></description>
										<content:encoded><![CDATA[
<p>The U.S. House passed a defense-policy bill on July 22, 2026, that incorporates President Donald Trump’s request for approximately $1.15 trillion in national-security spending and proposes renaming the Department of Defense as the Department of War.</p>

<p>The measure also includes a proposed pay raise for service members ranging from 5% to 7%, depending on rank. It addresses authority over the naming of military installations and other military property.</p>

<p>The action sets out major proposed changes to national defense priorities, military compensation and the institutional identity of the federal agency responsible for defense policy. But the legislation is not yet final law.</p>

<h2>What the House bill would do</h2>

<p>The spending figure in the measure is approximately $1.15 trillion in proposed national-security spending. The bill incorporates that request rather than establishing, by itself, final appropriated funding.</p>

<p>That distinction matters for readers and service members. The House action signals the level of national-security spending lawmakers are backing in this bill, but the approved record does not establish that the amount has become final funding.</p>

<p>The proposed service-member pay increase would range from 5% to 7%, with the specific increase depending on rank. The measure therefore ties compensation changes to the legislation’s broader defense-policy package rather than presenting the pay provision as a separately enacted change.</p>

<p>The bill also addresses military-installation and property naming authority. Under the proposal, that issue would be handled as part of the defense legislation, alongside spending and personnel provisions. The approved record does not provide a list of installations or properties affected by the naming language.</p>

<h2>Renaming the department</h2>

<p>The measure would designate the Department of Defense as the Department of War. Because the House action remains a congressional bill, the proposed designation should not be described as an effective legal change.</p>

<p>A change to the department’s name would have broad institutional and legal implications, according to the approved account of the legislation. Those implications are part of why the naming provision extends beyond a simple change in terminology: it could affect how the department is identified across federal military policy and related authorities if the language ultimately becomes law.</p>

<p>For now, however, the House passage establishes only that the proposal is included in the bill passed by that chamber. The available record does not confirm that the name has changed or that associated legal authorities have taken effect.</p>

<h2>What happens next</h2>

<p>The bill’s status remains unresolved in the approved record. It does not establish whether the Senate subsequently passed the same language or whether President Trump signed it.</p>

<p>That leaves several key questions open: whether the $1.15 trillion request remains in the final defense legislation, whether the 5% to 7% pay provisions survive, and whether the Department of War renaming language is included in enacted text. The final status of the renaming provision requires checking the enacted defense-authorization text, while the spending figure also would need to be distinguished from final appropriations.</p>

<p>No deadline for those next steps is established in the approved source record. Until there is confirmation of final congressional action and enactment, the spending level, pay raise, naming authority and department renaming remain proposals contained in a House-passed bill.</p>


<!-- esn-ng-sources:start -->
<section class="esn-ng-source-section"><h2>Sources</h2><ul class="esn-ng-sources"><li><a href="https://apnews.com/article/de65f6e0ee4f4d69699fb9f1f647083e">House votes for Department of War renaming as part of an annual defense bill</a><span class="esn-ng-source-organization">, Associated Press</span></li></ul></section>
<!-- esn-ng-sources:end -->
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/house-passes-defense-bill-backing-1-15-trillion-national-security-package-and-department-of-war-renaming/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">942898</post-id>	</item>
		<item>
		<title>FCC places California telecom company with Chinese links on national-security risk list</title>
		<link>https://111things.com/national/fcc-places-california-telecom-company-with-chinese-links-on-national-security-risk-list/</link>
					<comments>https://111things.com/national/fcc-places-california-telecom-company-with-chinese-links-on-national-security-risk-list/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Thu, 06 Aug 2026 22:22:10 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Science & Technology]]></category>
		<category><![CDATA[China Mobile]]></category>
		<category><![CDATA[communications security]]></category>
		<category><![CDATA[Digitalsystem Technology]]></category>
		<category><![CDATA[Federal Communications Commission]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[telecommunications regulation]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/local-headlines/fcc-places-california-telecom-company-with-chinese-links-on-national-security-risk-list/</guid>

					<description><![CDATA[The FCC added California-based Digitalsystem Technology to a national-security risk list on July 7, citing links to Chinese telecommunications firms and ownership by a Chinese national.]]></description>
										<content:encoded><![CDATA[
<p>The Federal Communications Commission added California-based Digitalsystem Technology to a list of companies it considers risks to U.S. national security on July 7, 2026, citing the company’s links to Chinese telecommunications firms and ownership by a Chinese national.</p>

<p>The action places Digitalsystem Technology within the FCC’s broader national-security and communications-authority process. That framework can affect whether a telecommunications provider receives or maintains federal authorization to provide services in the United States.</p>

<p>For now, the approved sources do not specify whether the designation has interrupted service, changed the company’s existing customer relationships or immediately canceled an authorization. They also do not identify a compliance deadline or implementation schedule for Digitalsystem Technology.</p>

<h2>What the designation means</h2>

<p>The FCC’s Covered List and related national-security process are intended to restrict communications equipment or providers that federal officials deem unacceptable security risks under federal communications law.</p>

<p>That makes the designation a regulatory decision with potential consequences for the company’s access to the federal authorization system. It is not, based on the approved materials, a finding that Digitalsystem Technology conducted espionage, hacked U.S. networks or carried out a cyberattack.</p>

<p>The distinction matters because a risk designation addresses the government’s judgment about communications security and authorization. The sources identify the FCC’s concerns about the company’s links and ownership, but they do not report a criminal finding against Digitalsystem Technology.</p>

<h2>Earlier FCC actions provide context</h2>

<p>The FCC’s action follows earlier commission decisions involving three Chinese carriers: China Mobile, China Telecom and China Unicom.</p>

<p>The three companies had previously been barred from providing international telecommunications services to the United States. Those actions show how the FCC has used its communications authority in response to national-security concerns involving telecommunications providers.</p>

<p>They do not establish that Digitalsystem Technology engaged in the same conduct or received the same sanction. The approved reporting supports the FCC’s stated rationale for the California company’s designation, but it does not describe a separate criminal or cyberattack case involving the company.</p>

<h2>Why communications resilience is part of the issue</h2>

<p>FCC materials frame communications security alongside the reliability and continuity of networks. That policy context includes broadband and next-generation 911, systems that support public communication and emergency response.</p>

<p>The connection does not mean the FCC has reported a failure of Digitalsystem Technology’s network or an effect on emergency services. Instead, it shows why the agency treats the security and continuity of communications infrastructure as related policy concerns.</p>

<p>For telecommunications companies, the immediate practical question is how the designation will be applied to Digitalsystem Technology’s ability to obtain or maintain federal authorization. For customers and other users, the available sources do not provide an impact figure, a required consumer action or evidence of an immediate service change.</p>

<h2>What happens next</h2>

<p>The next confirmed step will depend on how the FCC applies the determination to the company’s authorizations and services. The approved materials do not state an appeal date, compliance deadline or other announced implementation date.</p>

<p>The July 7 action therefore represents a new regulatory designation, not a documented customer shutdown or a criminal verdict. Its broader significance is the extension of the FCC’s effort to limit communications equipment and providers that it regards as unacceptable national-security risks while preserving the distinction between regulatory screening and proof of cybercrime.</p>


<!-- esn-ng-sources:start -->
<section class="esn-ng-source-section"><h2>Sources</h2><ul class="esn-ng-sources"><li><a href="https://www.marketscreener.com/news/fcc-denies-us-firm-with-chinese-links-approval-to-provide-telecom-services-ce7f5ed8dd8ff120">FCC denies US firm with Chinese links approval to provide telecom services</a><span class="esn-ng-source-organization">, Reuters</span></li><li><a href="https://docs.fcc.gov/public/attachments/DA-26-635A1.pdf">DA 26-635</a><span class="esn-ng-source-organization">, Federal Communications Commission</span></li><li><a href="https://docs.fcc.gov/public/attachments/DOC-422169A1.pdf">FCC-CIRC2606-03</a><span class="esn-ng-source-organization">, Federal Communications Commission</span></li></ul></section>
<!-- esn-ng-sources:end -->
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/fcc-places-california-telecom-company-with-chinese-links-on-national-security-risk-list/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">942426</post-id>	</item>
		<item>
		<title>Justice Department Seeks Role in Lawsuit Targeting xAI-Related Mississippi Data Center</title>
		<link>https://111things.com/national/justice-department-seeks-role-in-lawsuit-targeting-xai-related-mississippi-data-center/</link>
					<comments>https://111things.com/national/justice-department-seeks-role-in-lawsuit-targeting-xai-related-mississippi-data-center/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Thu, 06 Aug 2026 16:45:01 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Politics & Government]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Clean Air Act]]></category>
		<category><![CDATA[Environmental permitting]]></category>
		<category><![CDATA[Executive Power]]></category>
		<category><![CDATA[Justice Department]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=941908</guid>

					<description><![CDATA[The Justice Department has asked to intervene in a Clean Air Act lawsuit involving an xAI-related artificial-intelligence facility in Southaven, Mississippi, and wants the case dismissed. A federal hearing is scheduled for Aug. 24.]]></description>
										<content:encoded><![CDATA[
<p>The Justice Department has asked a federal court to let it join—and dismiss—a Clean Air Act lawsuit seeking to shut down or limit power operations at an xAI-related artificial-intelligence facility in Southaven, Mississippi.</p>

<p>The department’s Environment and Natural Resources Division filed the motion on June 15, 2026, in the U.S. District Court for the Northern District of Mississippi. The filing puts the federal government directly behind the facility’s continued operations while the court considers claims involving its power source.</p>

<p>The case has not been decided. The court had not ruled on the Justice Department’s request to intervene or its request for dismissal in the record reviewed for this article. The plaintiffs’ allegations and the department’s defenses remain disputed.</p>

<h2>What the lawsuit seeks</h2>

<p>The lawsuit alleges violations of the federal Clean Air Act involving the power source for the AI facility. The plaintiffs are seeking an injunction and damages, according to the Justice Department’s account of the case.</p>

<p>An injunction could impose limits on the operations at issue or otherwise require action while the litigation proceeds. The approved court record does not establish that the facility violated environmental law, and the Justice Department’s filing does not prove that the facility is exempt from permitting requirements.</p>

<p>Mississippi officials determined that no permit was required, according to the department’s filing. That state-level determination is part of the federal government’s position in the dispute; it is not a final ruling by the federal court on the plaintiffs’ claims.</p>

<h2>Why the Justice Department intervened</h2>

<p>The department argues that the facility’s AI work is important to the economy and to the Department of War’s national-defense mission. Its motion invokes federal interests in artificial intelligence and national defense as reasons for the government to participate in the case.</p>

<p>The filing is a concrete exercise of executive-branch legal authority. Rather than leaving the dispute solely to the private parties and state permitting officials, the federal government is asking to become a party and to end the lawsuit through dismissal.</p>

<p>That makes the case relevant beyond Southaven. It tests how federal intervention in litigation interacts with state environmental permitting while the administration promotes AI development and security. The dispute also illustrates the practical conflict that can arise when large computing facilities require power arrangements that become the subject of environmental litigation.</p>

<p>The administration’s AI executive order directs federal agencies and officials to promote AI innovation and security. The Justice Department’s motion presents the litigation through that broader federal policy framework, linking the facility’s work to economic and national-security priorities.</p>

<h2>What happens next</h2>

<p>The court has scheduled an evidentiary hearing on the plaintiffs’ motion for a preliminary injunction for Aug. 24, 2026. That hearing is the next known date in the case and concerns the plaintiffs’ request for interim court action.</p>

<p>The hearing does not predetermine whether the injunction will be granted or denied. The court also still must decide whether the Justice Department may intervene and whether the lawsuit should be dismissed. No outcome on those motions is established in the approved record.</p>

<p>For the parties, the immediate questions are whether the federal government will become an official participant in the case and whether the court will allow the Clean Air Act claims to proceed. For the public, the case provides an early test of how the administration’s AI priorities will be asserted in a federal court when they intersect with state permitting decisions and environmental claims.</p>


<!-- esn-ng-sources:start -->
<section class="esn-ng-source-section"><h2>Sources</h2><ul class="esn-ng-sources"><li><a href="https://www.justice.gov/opa/pr/justice-department-files-intervene-and-dismiss-lawsuit-would-hamper-americas-ai-innovation">Justice Department Files to Intervene and Dismiss Lawsuit that Would Hamper America’s AI Innovation and Security</a><span class="esn-ng-source-organization">, U.S. Department of Justice</span></li><li><a href="https://www.justice.gov/opa/media/1446141/dl?inline=">DOJ motion to intervene and dismiss</a><span class="esn-ng-source-organization">, U.S. Department of Justice</span></li></ul></section>
<!-- esn-ng-sources:end -->
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/justice-department-seeks-role-in-lawsuit-targeting-xai-related-mississippi-data-center/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">941908</post-id>	</item>
		<item>
		<title>Pentagon AI rollout races ahead of oversight deadlines</title>
		<link>https://111things.com/national/pentagon-ai-rollout-races-ahead-of-oversight-deadlines/</link>
					<comments>https://111things.com/national/pentagon-ai-rollout-races-ahead-of-oversight-deadlines/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 15:17:34 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[Government Accountability]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Pentagon]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=941611</guid>

					<description><![CDATA[The Pentagon is expanding AI use across classified systems while key oversight documents required by a June memorandum remain publicly unverified.]]></description>
										<content:encoded><![CDATA[<p>The Pentagon’s artificial-intelligence rollout is moving ahead of the first major oversight deadlines in President Donald Trump’s June 5 national-security memorandum, with new classified-network agreements and broad internal use of AI already announced.</p>
<p>The unresolved question is whether the controls required by that memorandum are advancing at the same pace.</p>
<p>National Security Presidential Memorandum 11 directs the Department of <a href="https://www.war.gov/News/Releases/Release/Article/4475177/classified-networks-ai-agreements/" rel="nofollow noopener" target="_blank">War</a> and intelligence agencies to accelerate national-security AI adoption while producing new rules for autonomous weapons, governance, procurement, security, training and testing. As of August 5, 2026, the public record reviewed does not confirm that the memorandum’s first required policy updates have been completed.</p>
<h2>What the memorandum requires</h2>
<p>NSPM-11 gives the Secretary of War 90 days to issue an update to Department of Defense Directive 3000.09, the directive governing autonomy in weapon systems. That makes September 3, 2026, the first major checkpoint.</p>
<p>The memorandum also requires the Committee on National Security Systems and the Office of Management and Budget, working with other national-security officials, to issue an AI governance policy and a classified annex within the same 90-day period. Within 120 days, it calls for additional work on procurement, access to computing capacity, industry security, data exchanges, training, risk management and testing. Those deadlines fall on October 3, 2026.</p>
<p>These are requirements and deadlines, not evidence that the resulting policies are already in force. <a href="https://www.whitehouse.gov/presidential-actions/2026/06/national-security-presidential-memorandum-nspm-11/" rel="nofollow noopener" target="_blank">The White House</a> memorandum does not by itself establish that the Department of War or other agencies have completed the required documents.</p>
<h2>Deployment is already expanding</h2>
<p>In a May 1 announcement, the Department of War said it had reached agreements with eight companies—SpaceX, OpenAI, Google, NVIDIA, Reflection, Microsoft, Amazon Web Services and Oracle—to deploy artificial-intelligence capabilities on classified networks.</p>
<p>The department also said more than 1.3 million personnel had used GenAI.mil during its first five months, generating tens of millions of prompts and deploying hundreds of thousands of AI agents.</p>
<p>A separate AI Acceleration Strategy describes three major efforts: Agent Network for AI-enabled battle management and decision support, GenAI.mil for department-wide access to frontier models, and Enterprise Agents for secure workflow deployment. The strategy also includes artificial-intelligence infrastructure and workforce initiatives.</p>
<p>The department’s announcements document expanding access and experimentation. They do not, by themselves, show that the programs satisfy NSPM-11’s procurement, governance or testing requirements.</p>
<p>The company count has differed across accounts. The Department of War’s May 1 release lists eight companies, while an Associated Press report described a separate seven-company arrangement and noted that Anthropic was absent from the department’s list. The accounts should not be treated as identical without additional documentation.</p>
<h2>Why Directive 3000.09 matters</h2>
<p>Directive 3000.09 is central to the debate because it addresses how autonomous and semi-autonomous weapon systems are developed, tested and used. The safeguards discussed in the directive and related oversight include human judgment, geographic limits, termination procedures, reliability and robustness testing, and protection against adversarial manipulation.</p>
<p>The pending update has drawn congressional scrutiny. In a June 12 letter, Sen. Ruben Gallego questioned whether a compressed rewrite could weaken human judgment, shorten testing, or increase risks involving friendly fire and civilian harm. He also asked about coordination with allies and protections for civilians in host nations.</p>
<p>Gallego’s letter is an oversight document and a set of questions, not a finding that wrongdoing has occurred. The available records also do not establish that autonomous weapons are currently operating without human control or that a specific deployment failure has occurred.</p>
<h2>Inspectors are reviewing open recommendations</h2>
<p>On June 29, the Department of Defense Office of <a href="https://media.defense.gov/2026/Jul/02/2003957330/-1/-1/1/D2026-DEV0SI-0108.000_REDACTED_FINAL.PDF" rel="nofollow noopener" target="_blank">Inspector General</a>, using the secondary title Department of War Inspector General, opened a follow-up evaluation of open recommendations concerning AI policy, governance, acquisition and implementation procedures.</p>
<p>The memorandum says the review will examine the status of recommendations from earlier evaluations, including work involving AI governance and acquisition. It also states that the use of the Department of War title does not change the Department of Defense’s statutory name, authorities or the inspector general’s responsibilities.</p>
<p>The evaluation is an active oversight action, not a final compliance finding. Its eventual conclusions could help clarify whether existing controls, acquisition practices and governance arrangements match the department’s expanding AI use.</p>
<h2>What remains unknown</h2>
<p>As of August 5, the public sources reviewed do not verify publication of the revised Directive 3000.09, the national-security AI governance policy, or the classified annex required by NSPM-11. Public records also do not establish whether the department’s announced programs have completed the memorandum’s related testing, risk-management, procurement and reporting steps.</p>
<p>Many details may remain classified, but the existence, status or public confirmation of the required policy documents would still be an important accountability marker.</p>
<h2>What to watch next</h2>
<p>September 3 will be the first visible test of whether deployment and oversight are moving together. Readers should watch for confirmation of the revised Directive 3000.09, the national-security AI governance policy, the status of its classified annex, and provisions governing human oversight, testing, geographic limits, termination and system robustness.</p>
<p>October 3 is the next major checkpoint for procurement, industry-security, data-exchange, training, risk-management and testing deliverables.</p>
<p>The issue reaches beyond classified facilities. Military AI decisions can affect servicemembers, allied forces, civilians in conflict zones, contractors, technology companies and taxpayers. The immediate public question is not whether the government is using AI. Official records show that it is. The accountability question is what documented safeguards and independent reviews accompany that use.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.whitehouse.gov/presidential-actions/2026/06/national-security-presidential-memorandum-nspm-11/" rel="nofollow noopener" target="_blank">National Security Presidential Memorandum/NSPM-11 — The White House</a></li>
<li><a href="https://www.war.gov/News/Releases/Release/Article/4475177/classified-networks-ai-agreements/" rel="nofollow noopener" target="_blank">Classified Networks AI Agreements — U.S. Department of War</a></li>
<li><a href="https://media.defense.gov/2026/Jul/02/2003957330/-1/-1/1/D2026-DEV0SI-0108.000_REDACTED_FINAL.PDF" rel="nofollow noopener" target="_blank">Follow-up Evaluation on Artificial Intelligence Recommendations — Inspector General</a></li>
<li><a href="https://apnews.com/article/pentagon-artificial-intelligence-military-classified-systems-war-060cecf836c4cebcf012a3ceb5333f2c" rel="nofollow noopener" target="_blank">U.S. military and 7 companies make deals to use AI in classified systems — Associated Press</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/pentagon-ai-rollout-races-ahead-of-oversight-deadlines/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">941611</post-id>	</item>
		<item>
		<title>White House AI framework reportedly excludes open-weight models</title>
		<link>https://111things.com/national/white-house-ai-framework-reportedly-excludes-open-weight-models/</link>
					<comments>https://111things.com/national/white-house-ai-framework-reportedly-excludes-open-weight-models/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 09:12:25 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[AI policy]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<category><![CDATA[White House]]></category>
		<guid isPermaLink="false">https://111things.com/?p=941294</guid>

					<description><![CDATA[The White House’s voluntary AI review plan reportedly covers closed frontier models, leaving open-weight systems outside a process whose details remain private.]]></description>
										<content:encoded><![CDATA[<p>The <a href="https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" rel="nofollow noopener" target="_blank">White House</a>’s newly completed voluntary framework for reviewing advanced artificial intelligence models will reportedly exclude open-weight systems, according to reports on private discussions with AI companies Tuesday, August 4.</p>
<p>The reported decision would make the administration’s pre-release safety process focus on closed, proprietary frontier models with advanced capabilities in areas such as cybersecurity and hacking. The White House said Monday, August 3, that it had completed the framework required by President Donald Trump’s June 2 executive order, but it has not released the document publicly.</p>
<h2>What the reported framework would cover</h2>
<p><a href="https://www.axios.com/2026/08/04/trump-ai-framework-open-models" rel="nofollow noopener" target="_blank">Axios</a> reported that administration officials described a covered frontier model as a closed-source system with state-of-the-art capabilities and national-security risks. The report said the framework does not publicly define what qualifies as “state-of-the-art” or how national-security risk would be measured.</p>
<p>During discussions with AI companies on August 4, the administration reportedly said open-weight models would not go through the same voluntary safety tests. <a href="https://www.reutersconnect.com/collection/refile-trump-administration-to-ask-us-ai-firms-to-voluntarily-submit-models-for-cybersecurity-tests/dGFnOnJldXRlcnMuY29tLDIwMjY6bmV3c21sX1ZBNTU2MDAzMDYyMDI2UlAx" rel="nofollow noopener" target="_blank">Reuters</a> separately reported that administration advisers told developers those models would be excluded from the testing process.</p>
<p>Open-weight models are systems whose core model weights or other components are made available for download or reuse. That differs from closed systems that remain under a company’s control and are typically accessed through the company’s infrastructure or an application programming interface.</p>
<p>The distinction matters because a company can provide temporary access to a closed model before release. Once an open-weight model is distributed, the original developer may have less ability to control who uses it, how it is modified or where it is deployed.</p>
<h2>Review would be voluntary and temporary</h2>
<p>The reported process would give the federal government access to covered models for up to 30 days before public release. Axios reported that models would be stored in high-security environments and that detailed logs would track who accessed them.</p>
<p>The framework is not a public regulation, and it does not create a general federal licensing system. Executive Order 14409, issued June 2, directs agencies to develop a voluntary framework with AI developers and to establish secure early access for trusted government partners.</p>
<p>The order also calls for a classified benchmarking process to assess advanced cyber capabilities and determine when a model qualifies as a covered frontier model. It expressly says the order does not authorize mandatory federal licensing, pre-clearance or permitting for the development, publication, release or distribution of AI models.</p>
<h2>What remains unknown</h2>
<p>The White House has not publicly confirmed the reported open-weight exclusion in an official framework document. Because the full framework and its detailed thresholds remain private, the public cannot yet determine exactly which models or developers would be included.</p>
<p>The reporting also does not establish that every open-source or foreign-developed model is categorically exempt. It specifically concerns open-weight models discussed during private meetings.</p>
<p>That leaves an unresolved policy question: whether a voluntary review process aimed at closed models can address comparable cybersecurity risks from powerful systems whose weights are released for wider reuse. Critics may view the distinction as a potential gap in federal oversight, but the scope and consequences cannot be fully assessed until the administration publishes guidance or clarifies the definitions.</p>
<h2>What developers and users should watch</h2>
<p>Businesses and developers using an open-weight model should not treat exclusion from the reported process as federal safety approval. The framework, as described, would be voluntary and would not certify models that fall outside it.</p>
<p>The next questions are whether the White House releases implementation guidance, identifies the officials responsible for reviews, explains the threshold for coverage and describes how open-weight systems will be handled when they present similar cybersecurity risks.</p>
<p>The administration’s separate national-security policy directs agencies to use and test both commercial and open-source AI technologies. That policy provides context for the debate, but it does not publicly resolve how open-weight models will be treated under the new pre-release framework.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.axios.com/2026/08/04/trump-ai-framework-open-models" rel="nofollow noopener" target="_blank">Axios: “Scoop: Inside Trump’s AI framework”</a></li>
<li><a href="https://www.reutersconnect.com/collection/refile-trump-administration-to-ask-us-ai-firms-to-voluntarily-submit-models-for-cybersecurity-tests/dGFnOnJldXRlcnMuY29tLDIwMjY6bmV3c21sX1ZBNTU2MDAzMDYyMDI2UlAx" rel="nofollow noopener" target="_blank">Reuters: “Trump advisers tell AI firms they will not safety-test open-weight models”</a></li>
<li><a href="https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" rel="nofollow noopener" target="_blank">White House: Executive Order 14409</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/white-house-ai-framework-reportedly-excludes-open-weight-models/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">941294</post-id>	</item>
		<item>
		<title>Jay Clayton Takes Over as Intelligence Chief After Senate Vote</title>
		<link>https://111things.com/national/jay-clayton-takes-over-as-intelligence-chief-after-senate-vote/</link>
					<comments>https://111things.com/national/jay-clayton-takes-over-as-intelligence-chief-after-senate-vote/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Wed, 05 Aug 2026 07:12:54 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Congressional oversight]]></category>
		<category><![CDATA[Jay Clayton]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Office of the Director of National Intelligence]]></category>
		<category><![CDATA[Senate]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=941202</guid>

					<description><![CDATA[Jay Clayton has taken over as national intelligence director after a 51-47 Senate vote, ending Bill Pulte’s temporary tenure and beginning a new oversight test.]]></description>
										<content:encoded><![CDATA[<p>Walter “Jay” Clayton III has taken over as director of national intelligence after the Senate confirmed him 51-47 on July 28 and acting director Bill Pulte transferred authority on August 3. The change gives the U.S. intelligence community Senate-confirmed leadership after roughly two months under an acting director.</p>
<p>The transition starts a closely watched test of whether Clayton can provide stable management while preserving the independence and credibility of intelligence assessments.</p>
<h2>What changed at the intelligence office</h2>
<p>Pulte became acting director after former DNI Tulsi Gabbard resigned. His temporary appointment drew concern from lawmakers because he led the Federal Housing Finance Agency and had no publicly established intelligence background, according to the <a href="https://apnews.com/article/trump-pulte-clayton-intelligence-director-541027bbe3a57c1b5510451de5e3161e" rel="nofollow noopener" target="_blank">Associated Press</a>.</p>
<p>Clayton brings a different background. He served as U.S. attorney for the Southern District of New York and previously chaired the Securities and Exchange Commission. The Senate confirmed him along party lines, with 51 senators voting for him and 47 against.</p>
<p>The August 3 transfer of authority ended Pulte’s acting tenure. The White House had not publicly announced details for when Clayton would be sworn in, so the handoff should not be described as a separately documented swearing-in ceremony.</p>
<h2>Why the DNI position matters</h2>
<p><a href="https://www.congress.gov/crs_external_products/IF/HTML/IF10470.html" rel="nofollow noopener" target="_blank">The director of national intelligence</a> does not exercise day-to-day operational control over every intelligence agency. The office provides oversight, direction, coordination and budgetary leadership across the intelligence community.</p>
<p>The Congressional Research Service says the DNI is responsible for oversight and direction of the intelligence community’s 18 elements, management of National Intelligence Program funds, cooperation among intelligence agencies and international partners, and priorities for intelligence collection, analysis and production.</p>
<p>The DNI also serves as the president’s principal intelligence adviser. That gives the office influence over how the government evaluates threats, coordinates information and briefs the president and Congress on national-security risks.</p>
<h2>Why Clayton’s confirmation was contentious</h2>
<p>Clayton’s July 15 confirmation hearing before the Senate Intelligence Committee focused on his qualifications and on whether he would maintain political independence in the intelligence process.</p>
<p>During questioning, Clayton repeatedly declined to say outright that Joe Biden won the 2020 presidential election. He referred to the election as “certified,” but did not give the direct answer some senators sought. The established outcome is that Biden won the 2020 election.</p>
<p>Democratic senators criticized those answers and questioned whether Clayton would keep intelligence analysis separate from political messaging. <a href="https://www.warner.senate.gov/newsroom/press-releases/senate-intel-vice-chair-warner-on-confirmation-of-jay-clayton-to-be-dni/" rel="nofollow noopener" target="_blank">Sen. Mark Warner</a>, the committee’s vice chair, later said he had serious reservations about whether Clayton would stand up to political pressure. Those are concerns and criticisms raised during the confirmation process, not a finding that Clayton has politicized intelligence or committed misconduct.</p>
<p>Republican senators described Clayton as qualified and pointed to his legal, government and national-security experience. The 51-47 vote showed that the nomination remained politically divisive rather than receiving bipartisan approval.</p>
<h2>What Congress will watch next</h2>
<p>The Senate Intelligence Committee’s oversight will be central to the next phase. Senators are likely to focus on whether Clayton provides candid briefings, protects analysts from political pressure and maintains clear standards for intelligence judgments.</p>
<p>Congress will also watch how Clayton manages National Intelligence Program funds, coordinates the 18 intelligence-community elements under the DNI’s oversight and responds when intelligence assessments conflict with political claims from the White House or other officials.</p>
<p>Clayton’s actual management approach remains unresolved. His priorities, relationship with the White House and working relationship with Congress will become clearer through future guidance, budget decisions, public statements and classified briefings.</p>
<p>For most households, the immediate effect is unlikely to appear as a new policy or service. The accountability question is more basic: whether permanent leadership brings continuity to the intelligence community without weakening the independence that gives its assessments credibility.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://apnews.com/article/trump-pulte-clayton-intelligence-director-541027bbe3a57c1b5510451de5e3161e" rel="nofollow noopener" target="_blank">Associated Press — Clayton takes over after Pulte’s acting tenure</a></li>
<li><a href="https://www.congress.gov/crs_external_products/IF/HTML/IF10470.html" rel="nofollow noopener" target="_blank">Congressional Research Service — The Director of National Intelligence</a></li>
<li><a href="https://www.warner.senate.gov/newsroom/press-releases/senate-intel-vice-chair-warner-on-confirmation-of-jay-clayton-to-be-dni/" rel="nofollow noopener" target="_blank">Sen. Mark Warner — Statement on Clayton’s confirmation</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/jay-clayton-takes-over-as-intelligence-chief-after-senate-vote/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">941202</post-id>	</item>
		<item>
		<title>White House flags aircraft imports as national-security concern</title>
		<link>https://111things.com/national/white-house-flags-aircraft-imports-as-national-security-concern/</link>
					<comments>https://111things.com/national/white-house-flags-aircraft-imports-as-national-security-concern/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Tue, 04 Aug 2026 11:18:06 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Aviation]]></category>
		<category><![CDATA[Federal Policy]]></category>
		<category><![CDATA[Manufacturing]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Trade]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=940069</guid>

					<description><![CDATA[President Donald Trump identified commercial aircraft and engine imports as a national-security concern, but imposed no immediate tariffs as agencies begin talks.]]></description>
										<content:encoded><![CDATA[<p>The White House has identified imported commercial aircraft, jet engines and related parts as a national-security concern, but President Donald Trump’s July 9 proclamation does not impose new tariffs.</p>
<p>Instead, the proclamation starts a negotiation and monitoring phase. The <a href="https://www.commerce.gov/news/fact-sheets/2017/04/fact-sheet-section-232-investigations-effect-imports-national-security" rel="nofollow noopener" target="_blank">Commerce</a> Department and the U.S. Trade Representative are directed to pursue or continue talks with foreign trading partners and provide the president with an update within 180 days. Counting from July 9, 2026, that deadline falls approximately on January 5, 2027.</p>
<h2>What changed on July 9</h2>
<p>Trump accepted the Commerce Department’s finding under Section 232 of the Trade Expansion Act that commercial aircraft, jet engines and associated parts are being imported in quantities or under circumstances that threaten to impair U.S. national security.</p>
<p>The proclamation describes the covered supply chain as important to commercial aviation, cargo transportation, tourism, defense-related operations and maintenance, repair and overhaul services. It also says commercially derived aircraft, engines and parts support some military operations and transportation requirements.</p>
<p>The immediate policy decision is narrower than a new aircraft tariff. The proclamation adopts negotiations rather than immediate Section 232 duties and says the administration may consider alternative remedies later, depending on the status or outcome of those talks.</p>
<h2>Why the administration cited national security</h2>
<p>The administration’s rationale focuses on the resilience of the aerospace industrial base, not only on ordinary trade competition.</p>
<p>The proclamation says the Commerce investigation identified reliance on foreign supply chains, vulnerability to disruptions or foreign pressure, and quality-control and counterfeiting risks involving imported components. It also cites underused domestic manufacturing capacity, a declining qualified workforce, industry consolidation and higher production costs.</p>
<p>Those are findings and assertions in the Commerce investigation and presidential proclamation. The documents do not establish that aircraft prices, airline fares or delivery schedules have already changed because of this action.</p>
<h2>What Section 232 allows</h2>
<p>Section 232 permits the president to adjust imports when an investigation finds that their quantity or circumstances threaten to impair U.S. national security. The statute can support negotiations, import monitoring and later measures such as tariffs or other import restrictions.</p>
<p>In this case, the administration chose negotiations first. That leaves the current import rules unchanged while agencies assess whether agreements with trading partners address the concerns identified by Commerce.</p>
<h2>Who could be affected</h2>
<p>Airlines, cargo operators, aircraft manufacturers, engine makers, parts suppliers and maintenance providers are the businesses most directly connected to the policy.</p>
<p>There is no immediate new federal tariff from the July 9 proclamation. Future trade restrictions, if proposed and adopted, could affect aircraft and engine costs, sourcing decisions, maintenance operations and delivery schedules. Those effects remain possible rather than established.</p>
<h2>What to watch next</h2>
<p>Commerce must continue monitoring imports and inform the president if conditions indicate a need for further Section 232 action. Commerce and USTR must also provide an update on negotiations within 180 days of the proclamation.</p>
<p>The next major checkpoint is therefore an administration progress update due approximately January 5, 2027. Until then, the key developments will be agency guidance, announcements about trading-partner negotiations and any proposed remedy.</p>
<p><strong>Bottom line:</strong> The White House has formally labeled aircraft and engine imports a national-security concern and opened a negotiation framework. For now, airlines and aerospace companies face no new tariff from this action, but future import restrictions remain possible if negotiations fail or are deemed ineffective.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.whitehouse.gov/presidential-actions/2026/07/adjusting-imports-of-commercial-aircraft-jet-engines-and-aircraft-and-engine-parts-into-the-united-states/" rel="nofollow noopener" target="_blank">White House proclamation on commercial aircraft and engine imports</a></li>
<li><a href="https://www.marketscreener.com/news/us-ends-probe-into-imported-airplanes-parts-without-seeking-new-tariffs-ce7f5ededd8ff02d" rel="nofollow noopener" target="_blank">Reuters report on the aircraft-import investigation</a></li>
<li><a href="https://www.commerce.gov/news/fact-sheets/2017/04/fact-sheet-section-232-investigations-effect-imports-national-security" rel="nofollow noopener" target="_blank">Commerce Department Section 232 fact sheet</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/white-house-flags-aircraft-imports-as-national-security-concern/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">940069</post-id>	</item>
		<item>
		<title>Section 702 expired in June. Why surveillance continues</title>
		<link>https://111things.com/national/section-702-expired-in-june-why-surveillance-continues/</link>
					<comments>https://111things.com/national/section-702-expired-in-june-why-surveillance-continues/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Mon, 03 Aug 2026 18:33:26 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[FBI]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Surveillance]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=937534</guid>

					<description><![CDATA[Section 702 lapsed on June 12, but existing court certifications may remain in effect as Congress debates reauthorization, FBI searches and privacy safeguards.]]></description>
										<content:encoded><![CDATA[<p>Section 702 of the Foreign Intelligence Surveillance Act lapsed at midnight on June 12, 2026, after the House rejected a short-term extension the day before. But that statutory lapse did not immediately switch off every activity connected to the surveillance program.</p>
<p>Existing Foreign Intelligence Surveillance Court certifications and related directives can remain operative under their stated terms. Rep. Warren <a href="https://davidson.house.gov/2026/6/davidson-statement-on-lapse-of-fisa-section-702" rel="nofollow noopener" target="_blank">Davidson</a>, R-Ohio, said in a June 12 statement that the certifications then in place would continue through March 2027. That date should not be read as a universal expiration date for every Section 702-related authorization.</p>
<p>The distinction matters because Congress is now debating what comes next: whether to reauthorize the authority, whether to require a warrant before the <a href="https://www.fbi.gov/news/speeches-and-testimony/oversight-of-section-702-of-the-foreign-intelligence-surveillance-act-and-related-surveillance-authorities" rel="nofollow noopener" target="_blank">FBI</a> searches Section 702 information using an American&#8217;s identifier, and how to strengthen reporting and compliance rules.</p>
<h2>What changed on June 12</h2>
<p>Section 702 permits the government to collect foreign-intelligence information by targeting certain people outside the United States. Congress must periodically authorize the program, and the House did not pass a short-term extension before the June 12 deadline.</p>
<p>The result was a lapse in the statute&#8217;s current congressional authorization. It was not, however, an immediate termination of all collection, storage or related activity conducted under certifications and directives approved before the lapse. The precise legal and operational effects of the lapse remain part of the congressional and legal debate.</p>
<p>That leaves lawmakers facing a renewal decision rather than a simple restart. Congress could enact a long-term reauthorization, attach new privacy and oversight conditions, or allow existing certifications to run toward their stated expiration while negotiations continue.</p>
<h2>How Section 702 affects Americans</h2>
<p>Section 702 is designed to target non-U.S. persons reasonably believed to be outside the United States for foreign-intelligence purposes. Americans are not supposed to be the targets of that collection.</p>
<p>Americans&#8217; communications can nevertheless be collected incidentally when they communicate with a foreign target or appear in information connected to a foreign target. A later search of stored Section 702 information is called a query. The FBI says a query does not create new collection; it searches information the government already acquired.</p>
<p>Under existing procedures, the FBI may use U.S.-person query terms such as a name, email address or telephone number. The FBI says such a query must have an authorized purpose, be reasonably designed for that purpose and have a specific factual basis indicating that it is reasonably likely to retrieve foreign-intelligence information or, in limited circumstances, evidence of a crime.</p>
<h2>What the 2025 numbers show</h2>
<p>The Office of the Director of National Intelligence estimated that 349,823 non-U.S. persons were targeted under Section 702 in calendar year 2025, up from 291,824 in 2024.</p>
<p>The <a href="https://www.odni.gov/files/CLPT/documents/2026_ASTR_for_CY2025.pdf" rel="nofollow noopener" target="_blank">ODNI</a> report also counted 7,413 FBI U.S.-person query terms in 2025, compared with 5,518 in 2024. A query term is an identifier used to search the data. The figure does not necessarily represent 7,413 unique Americans, investigations or successful accesses to communications.</p>
<p>ODNI separately reported 1,081 FBI U.S.-person evidence-of-a-crime-only queries conducted for discovery purposes. FBI users accessed results in 245 of those queries. Those figures do not mean that 1,081 Americans were surveilled, charged or prosecuted. They describe searches of Section 702-acquired information under the reporting categories used by the government.</p>
<p>ODNI said the evidence-of-a-crime-only category is limited under the Reforming Intelligence and Securing America Act, which largely restricted that type of FBI query while retaining exceptions. The report also cautioned that year-to-year figures can change with litigation, criminal matters, operational priorities and other factors.</p>
<h2>What safeguards exist</h2>
<p>The FBI says its safeguards include case-specific justifications for U.S.-person queries, mandatory training, audits and recurring reviews by the Justice Department and ODNI. It also requires enhanced review for certain sensitive queries involving categories such as elected officials, members of the media, academics and religious figures.</p>
<p>The FBI has acknowledged serious past compliance problems, including improper queries involving Americans who took part in peaceful protests. The agency says reforms adopted beginning in 2021 added opt-in controls for unminimized information, attorney approval for large batch queries and stronger documentation requirements.</p>
<p>Those safeguards are the government&#8217;s account of its current compliance framework. Privacy advocates and lawmakers seeking additional restrictions argue that internal rules and executive-branch oversight do not provide enough protection, particularly when Americans&#8217; information is searched without a traditional warrant.</p>
<h2>What Congress is arguing over</h2>
<p>The most prominent dispute is whether reauthorization should require a warrant before the government searches Section 702 information using an American&#8217;s identifier. That is a proposed reform, not current law.</p>
<p>Supporters of the program say U.S.-person queries can help identify Americans who are victims of foreign hacking, espionage, terrorism, kidnapping or other threats. The FBI has argued that a broad warrant requirement could delay the use of information already lawfully collected.</p>
<p>Critics say searching Americans&#8217; communications without a warrant creates a serious Fourth Amendment concern, even when the original target was overseas. Other potential reforms include putting FBI compliance policies into statute, expanding reporting to Congress, tightening provider obligations and increasing penalties for violations.</p>
<p>No replacement framework was established by the June lapse itself.</p>
<h2>What to watch next</h2>
<p>The next important markers are any bill to reauthorize Section 702, congressional oversight hearings, new court filings and additional transparency reports. Davidson identified March 2027 as the point through which the existing certifications and directives would continue, but the timing and scope of any future certifications could depend on further legal and congressional action.</p>
<p>For the public, the immediate question is not whether every surveillance activity stopped on June 12. It is what Congress will authorize next and whether lawmakers require a warrant, stronger reporting or other controls before restoring the statute.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.odni.gov/files/CLPT/documents/2026_ASTR_for_CY2025.pdf" rel="nofollow noopener" target="_blank">ODNI Annual Statistical Transparency Report for Calendar Year 2025</a></li>
<li><a href="https://davidson.house.gov/2026/6/davidson-statement-on-lapse-of-fisa-section-702" rel="nofollow noopener" target="_blank">Rep. Warren Davidson statement on the lapse of FISA Section 702</a></li>
<li><a href="https://apnews.com/article/fisa-bill-pulte-trump-democrats-spy-powers-066052a8521d68215497c1162f3dbd6c" rel="nofollow noopener" target="_blank">Associated Press: Congress fails to extend FISA spy tool as deadline closes in</a></li>
<li><a href="https://www.fbi.gov/news/speeches-and-testimony/oversight-of-section-702-of-the-foreign-intelligence-surveillance-act-and-related-surveillance-authorities" rel="nofollow noopener" target="_blank">FBI: Oversight of Section 702 and Related Surveillance Authorities</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/section-702-expired-in-june-why-surveillance-continues/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">937534</post-id>	</item>
		<item>
		<title>GAO flags delays in federal watchdog misconduct reviews</title>
		<link>https://111things.com/national/gao-flags-delays-in-federal-watchdog-misconduct-reviews/</link>
					<comments>https://111things.com/national/gao-flags-delays-in-federal-watchdog-misconduct-reviews/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Mon, 03 Aug 2026 12:28:36 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[accountability]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[Government Oversight]]></category>
		<category><![CDATA[Inspectors General]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=937207</guid>

					<description><![CDATA[A GAO review found missed deadlines, incomplete records and weak congressional reporting in the system that investigates misconduct allegations against senior federal watchdog officials.]]></description>
										<content:encoded><![CDATA[<p>House <a href="https://oversight.house.gov/release/comer-sessions-higgins-biggs-continue-oversight-of-cigie-following-gao-report-uncovering-integrity-committee-failures/" rel="nofollow noopener" target="_blank">Oversight</a> leaders are demanding records from the Council of the Inspectors General on Integrity and Efficiency after a federal review found repeated delays and documentation gaps in the system used to investigate misconduct allegations involving senior inspectors-general officials.</p>
<p>The committee’s July 1, 2026, letter to CIGIE Chair Cheryl Mason says lawmakers are considering whether to remove or modify CIGIE’s responsibility for investigating wrongdoing within inspectors-general offices. That possibility remains under consideration; no legislative change has been enacted.</p>
<h2>What the Integrity Committee does</h2>
<p>CIGIE’s Integrity Committee handles noncriminal allegations involving covered senior-level personnel in federal inspectors-general offices. Covered officials can include inspectors general and certain senior employees who report directly to an inspector general.</p>
<p>Those offices audit and investigate federal agencies, examine fraud and waste, and assess whether government programs are operating effectively and lawfully. The Integrity Committee can refer criminal allegations or prohibited-personnel-practice matters to other entities, including the Justice Department or the Office of Special Counsel.</p>
<p>The <a href="https://www.gao.gov/products/gao-26-107922" rel="nofollow noopener" target="_blank">GAO</a> review did not conclude that a particular intelligence-community investigation was mishandled. Its national-security relevance is broader: the report examines the process used to hold senior officials in oversight offices accountable, including officials connected to agencies with sensitive missions.</p>
<h2>What GAO reviewed</h2>
<p>The Government Accountability Office published its report May 14, 2026, and publicly released it June 15. The review covered fiscal year 2021 through the first half of fiscal year 2025.</p>
<p>During that period, the Integrity Committee received 16,245 complaints. Of those, 460 became cases referred for committee review, and the committee completed 15 investigative reports.</p>
<p>GAO used generalizable samples to assess complaint intake and case-review processes. It also examined five completed investigations selected judgmentally. GAO said that five-case sample was not statistically representative and cannot be used to draw conclusions about every completed investigation.</p>
<h2>Where the process broke down</h2>
<p>GAO estimated that 24 percent of sampled cases met all applicable time requirements for opening and review. The finding does not mean that 76 percent of all complaints were mishandled. It applies to the sampled cases used to test the committee’s intake and review procedures.</p>
<p>The report also found that the committee lacked a required secondary legal review for complaints labeled potentially frivolous. Under the committee’s procedures, legal counsel was supposed to review the program manager’s decision. GAO said the missing review could allow a complaint with merit to be screened out without the committee having a full opportunity to consider it.</p>
<p>The committee also did not consistently document required information, including recusals by members with potential conflicts of interest. GAO estimated, however, that 97 percent of complainants in the relevant sample received an immediate acknowledgment that their complaint had been received.</p>
<h2>Investigations exceeded the statutory deadline</h2>
<p>None of the five completed investigations GAO examined met the statutory 150-day completion deadline. The investigations took between 427 days and 1,246 days—roughly 14 months to more than three years.</p>
<p>Because the five investigations were selected judgmentally, the results are not a statistical estimate for all Integrity Committee investigations. They do show that every investigation in GAO’s selected sample exceeded the statutory deadline.</p>
<p>GAO also found that the Integrity Committee did not always provide Congress with required status information when investigations passed 150 days. The Inspector General Act requires CIGIE to provide semiannual reports to Congress on the status and progress of investigations, and GAO identified instances in which required updates were missing.</p>
<p>Assisting inspectors-general offices, which conducted investigations for the committee, failed to provide required monthly status updates in 37 of 90 instances reviewed. GAO said the missing updates limited the committee’s ability to oversee those investigations.</p>
<h2>Records and conclusions also raised concerns</h2>
<p>In some cases, final Integrity Committee reports did not explain differences between the committee’s conclusions and those of the assisting inspector-general office. GAO also identified weaknesses in records supporting investigation-related reimbursements, including documentation of labor and other costs and the review and approval of reimbursement requests.</p>
<p>These are process and accountability findings. GAO did not determine that any particular complaint was valid, that a named official committed wrongdoing, or that a specific national-security investigation was compromised.</p>
<h2>What happens next</h2>
<p>GAO issued eight recommendations covering complaint screening, deadlines, recusals, congressional reporting, oversight of assisting offices, reimbursement records and explanations for differing investigative conclusions. CIGIE agreed with the recommendations and described planned actions, but GAO lists the recommendations as open pending confirmation of implementation.</p>
<p>House Oversight’s July 1 letter requested a list of corrective actions, communications about congressional information requests, a detailed response plan and suggestions for possible congressional action. The committee requested the materials by July 15, 2026, and said it may consider legislative changes to the Integrity Committee’s role.</p>
<p>The next meaningful developments are CIGIE’s documented implementation of GAO’s recommendations, its response to congressional demands and any hearing or bill addressing how misconduct allegations against senior watchdog officials should be investigated.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://www.gao.gov/products/gao-26-107922" rel="nofollow noopener" target="_blank">GAO: Inspectors General Integrity Committee report</a></li>
<li><a href="https://files.gao.gov/reports/GAO-26-107922/index.html" rel="nofollow noopener" target="_blank">GAO-26-107922 full report text</a></li>
<li><a href="https://oversight.house.gov/release/comer-sessions-higgins-biggs-continue-oversight-of-cigie-following-gao-report-uncovering-integrity-committee-failures/" rel="nofollow noopener" target="_blank">House Oversight July 1 CIGIE oversight release</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/gao-flags-delays-in-federal-watchdog-misconduct-reviews/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">937207</post-id>	</item>
		<item>
		<title>Federal Reserve watchdog finds gaps in insider-risk controls</title>
		<link>https://111things.com/national/federal-reserve-watchdog-finds-gaps-in-insider-risk-controls/</link>
					<comments>https://111things.com/national/federal-reserve-watchdog-finds-gaps-in-insider-risk-controls/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Mon, 03 Aug 2026 09:48:22 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Federal Reserve]]></category>
		<category><![CDATA[Insider Risk]]></category>
		<category><![CDATA[Inspector General Reports]]></category>
		<category><![CDATA[Monetary Policy]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=937046</guid>

					<description><![CDATA[A Federal Reserve watchdog found major gaps in controls protecting sensitive economic information as a former adviser was sentenced in a related case.]]></description>
										<content:encoded><![CDATA[<p>The Federal Reserve’s internal watchdog found that the central bank’s controls were not sufficient to proactively identify and manage insider risks to sensitive economic information and other assets.</p>
<p>The finding appears in Board Report 2026-MO-B-010R, “The Board Needs a More Robust Insider Risk Management Program,” issued July 15, 2026. The report was released the same day the <a href="https://www.justice.gov/opa/pr/former-adviser-federal-reserve-board-governors-sentenced-federal-prison-term" rel="nofollow noopener" target="_blank">Justice</a> Department announced that former Federal Reserve senior adviser John Harold Rogers had been sentenced to 38 months in federal prison in a case involving restricted Federal Reserve information.</p>
<h2>What the inspector general found</h2>
<p>The Federal Reserve Office of Inspector General said the Board’s insider-risk management activities did not proactively or effectively identify and manage risks to the agency’s information and assets. The <a href="https://oig.federalreserve.gov/reports/board-insider-risk-management-redacted-jul2026.htm" rel="nofollow noopener" target="_blank">OIG</a> said the activities were not consistent with leading practices and identified a maturity gap compared with a peer federal financial regulatory agency.</p>
<p>The watchdog identified five principal gaps:</p>
<ul>
<li>No process for identifying the Board’s critical assets.</li>
<li>No centralized insider-risk program to proactively identify and manage threats at the enterprise level.</li>
<li>Insufficient procedures for timely internal information sharing, including information shared with the Federal Reserve System.</li>
<li>No consistent, enterprise-level policies and procedures for incident response and reporting.</li>
<li>No insider-risk training requirement for all Board staff.</li>
</ul>
<p>The OIG issued nine recommendations intended to create a more robust insider-risk management program. In its response to the draft report, the Board concurred with the recommendations and outlined actions to address each one. The OIG said it will follow up to determine whether the recommendations are fully addressed.</p>
<h2>Why Federal Reserve information matters</h2>
<p>The Board holds proprietary economic information, including restricted, nonpublic material related to monetary policy and the Federal Open Market Committee. Advance access to such information could be valuable to traders, foreign governments and others seeking insight into U.S. interest-rate decisions and the broader direction of the economy.</p>
<p>The OIG said foreign adversaries have an interest in the Board’s proprietary information because risks to that information could undermine U.S. competitiveness and potentially harm the U.S. economy. The report identifies weaknesses in management controls; it does not establish that current Federal Reserve information is being actively compromised or that a specific ongoing foreign operation is underway at the Board.</p>
<p>The review focused on the Board’s governance and management of its insider-risk activities, along with information sharing and coordination between the Board and the Federal Reserve System. The OIG said it did not assess insider-risk activities conducted by the individual Federal Reserve Banks.</p>
<h2>The Rogers case</h2>
<p>Rogers, 64, was sentenced in federal court to 38 months in prison and 12 months of supervised release. A federal jury found him guilty on Feb. 3, 2026, of making false statements to investigators from the Federal Reserve Board’s Office of Inspector General.</p>
<p>According to the Justice Department, Rogers worked as a senior adviser in the Board’s Division of International Finance from 2010 through 2021. Court papers described him as having access to restricted, nonpublic information about monetary policy and the Federal Open Market Committee.</p>
<p>The Justice Department said the case involved Rogers sharing restricted Federal Reserve information with Chinese intelligence operatives and then lying to investigators about those disclosures. The department said he sent sensitive material to personal accounts and shared information with people connected to China’s intelligence services.</p>
<p>Rogers was convicted of making false statements, not espionage. The criminal case and the OIG’s management review are related in timing and subject matter, but they are distinct: the sentencing concerns Rogers’s proven criminal conduct, while the audit addresses weaknesses in the Federal Reserve Board’s internal controls.</p>
<h2>What to watch next</h2>
<p>The key accountability question is whether the Federal Reserve completes the actions it outlined in response to the OIG’s nine recommendations.</p>
<p>Those actions could include a formal process for identifying critical information and assets, stronger enterprise-level governance, consistent incident-response and reporting rules, improved information sharing and mandatory insider-risk training for staff.</p>
<p>The OIG said it will conduct follow-up work. Until that oversight is complete, the public record shows a control system the watchdog found insufficient, a set of recommended corrective actions the Board accepted, and no final finding in this report that current Federal Reserve information is being actively compromised.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://oig.federalreserve.gov/reports/board-insider-risk-management-redacted-jul2026.htm" rel="nofollow noopener" target="_blank">Federal Reserve OIG: The Board Needs a More Robust Insider Risk Management Program</a></li>
<li><a href="https://www.justice.gov/opa/pr/former-adviser-federal-reserve-board-governors-sentenced-federal-prison-term" rel="nofollow noopener" target="_blank">U.S. Department of Justice: Former Adviser to Federal Reserve Board of Governors Sentenced</a></li>
<li><a href="https://news.bloomberglaw.com/banking-law/feds-watchdog-warns-on-insider-risk-after-china-secrets-case" rel="nofollow noopener" target="_blank">Bloomberg Law: Fed’s Watchdog Warns on Insider Risk After China Secrets Case</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/federal-reserve-watchdog-finds-gaps-in-insider-risk-controls/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">937046</post-id>	</item>
		<item>
		<title>House Intelligence Bill Would Give IC Inspector General New Powers</title>
		<link>https://111things.com/national/house-intelligence-bill-would-give-ic-inspector-general-new-powers/</link>
					<comments>https://111things.com/national/house-intelligence-bill-would-give-ic-inspector-general-new-powers/#respond</comments>
		
		<dc:creator><![CDATA[Brian Bateman]]></dc:creator>
		<pubDate>Mon, 03 Aug 2026 06:27:55 +0000</pubDate>
				<category><![CDATA[National]]></category>
		<category><![CDATA[Congress]]></category>
		<category><![CDATA[Federal Oversight]]></category>
		<category><![CDATA[Inspectors General]]></category>
		<category><![CDATA[Intelligence community]]></category>
		<category><![CDATA[National Security]]></category>
		<category><![CDATA[United States]]></category>
		<guid isPermaLink="false">https://111things.com/?p=936906</guid>

					<description><![CDATA[A House committee advanced a bill that would give the intelligence community’s watchdog new law-enforcement authority. The proposal is not yet law.]]></description>
										<content:encoded><![CDATA[<p>The <a href="https://intelligence.house.gov/2026/07/20/house-intelligence-committee-passes-fy2027-intelligence-authorization-act-out-of-committee/" rel="nofollow noopener" target="_blank">House Intelligence Committee</a> advanced legislation July 20 that would give the Intelligence Community Inspector General new law-enforcement authority, including powers intended to help preserve evidence, compel testimony and support criminal investigations.</p>
<p>The proposal is part of H.R. 9624, the Intelligence Authorization Act for Fiscal Year 2027. It remains proposed legislation, not current law. The bill would still need to move through the full House and Senate, survive negotiations over final language and be signed by the president before the change could take effect.</p>
<h2>What changed on July 20</h2>
<p>The House Permanent Select Committee on Intelligence passed the fiscal 2027 authorization bill out of committee on July 20. In its public summary, the committee identified law-enforcement authority for the Intelligence Community Inspector General as a provision intended to strengthen the detection of fraud, waste and mismanagement across the intelligence community.</p>
<p>The provision appears in Section 324 of the committee bill. The text would amend the National Security Act to state that Section 406(f) of Title 5 of the U.S. Code applies to the Office of the Inspector General of the Intelligence Community.</p>
<p>In plain language, the cross-reference is intended to extend law-enforcement authorities that other federal inspector-general offices use in criminal investigations. The exact effect would depend on the final enacted language and subsequent implementation. The authority does not exist for the IC Inspector General under the committee bill alone.</p>
<h2>Why the inspector general says the change matters</h2>
<p>Christopher Fox, the current Intelligence Community Inspector General, submitted a written statement for a closed House Intelligence Committee hearing on June 24. Fox said his office can face delays when it needs to coordinate with the Justice Department or FBI before taking investigative steps.</p>
<p>Fox wrote that the office has statutory access to information, individuals and facilities needed for oversight, but argued that access is difficult to enforce without law-enforcement authority. He said the current system can make it harder to preserve evidence, compel testimony and move quickly while records and investigative leads remain available.</p>
<p>One example in Fox’s statement involved an intelligence community employee who, according to Fox, purchased illegal firearm components from a Chinese company. Fox wrote that investigators could not act directly and waited 19 months for the Justice Department to decline prosecution. During that period, he said, the employee retained a position and security clearance. Fox presented the account as an example of an investigative limitation; the public statement does not establish a court finding or criminal conviction.</p>
<p>Fox also described an investigation opened in March 2021 involving a former senior intelligence official and alleged post-employment communications with current intelligence community employees about contracts worth tens of millions of dollars. Fox wrote that investigators could not compel testimony and had to coordinate with the Justice Department before an initial subject interview. The official was first interviewed in December 2024, more than three years after the investigation opened. Fox said a civil settlement through the Justice Department was imminent.</p>
<h2>What the office does now</h2>
<p>The Intelligence Community Office of the Inspector General was formally created within the Office of the Director of National Intelligence in 2010. <a href="https://www.odni.gov/accountability/" rel="nofollow noopener" target="_blank">ODNI</a> describes the office’s mission as conducting independent and objective audits, investigations, inspections and reviews across the intelligence community while promoting efficiency and detecting fraud, waste and mismanagement.</p>
<p>The office also accepts complaints involving criminal acts, misconduct, unauthorized disclosures and retaliation against whistleblowers. ODNI identifies Fox as the current inspector general and says the Senate confirmed him on October 7, 2025.</p>
<p>Fox said his office lacks criminal investigators with the training and experience needed to ensure some cases are developed in a prosecutable way. He wrote that potentially actionable criminal conduct may therefore be handled through administrative investigations instead.</p>
<h2>What happens next</h2>
<p>Committee passage does not send the bill directly to the president. The House must decide whether to schedule floor action. The Senate would then need to consider its own version or the House-passed measure, and lawmakers could negotiate changes before a final bill reaches the White House.</p>
<p>The next indicators are House floor scheduling, Senate committee or floor action, revisions to Section 324 and any final authorization agreement. Until those steps are completed and the president signs a final bill, the Intelligence Community Inspector General does not have the proposed new powers.</p>
<h2>Sources</h2>
<ul>
<li><a href="https://intelligence.house.gov/2026/07/20/house-intelligence-committee-passes-fy2027-intelligence-authorization-act-out-of-committee/" rel="nofollow noopener" target="_blank">House Intelligence Committee: FY2027 authorization bill</a></li>
<li><a href="https://www.odni.gov/accountability/" rel="nofollow noopener" target="_blank">ODNI: Intelligence Community Inspector General</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://111things.com/national/house-intelligence-bill-would-give-ic-inspector-general-new-powers/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">936906</post-id>	</item>
	</channel>
</rss>
