The Red Tape Roundup

A newsletter header image on a worn aged parchment paper texture background in muted beige cream and dark gray tones. In the center of the image is a bold serif font title. The title text reads exactly: "The Red Tape Roundup" — that is four words total. Line one: "The Red Tape" and line two: "Roundup" — where Roundup is spelled R then O then U then N then D then U then P. The text is deep crimson red. There are thin horizontal decorative lines above and below the title block. The style is archival editorial documentary. No people. No photography. Minimal and clean.

Weekly Investigative Briefing | November 14–20, 2026

A Note from the Editor

Holy smokes, what a week this has been!

This week, the world saw more than seven incidents causing service outages at Microsoft, the FAA, Chase, Bank of America, Wells Fargo, US Bank, Apple Pay, and even Zelle customers experienced disruptions. Another notable outage happened with the NSA Net, which appears to be some classified internal network used at the National Security Agency.

It is certainly an odd string of events happening all at once…

The FAA grounded flights because of a router failure caused by wiring upgrades in Arkansas.

Microsoft blames their Outlook, Exchange Online, and Teams outages on a technical fault, also during an upgrade.

DNI Jay Clayton attributed the NSA Net outage to an emergency patch related to PHP, a vulnerability which was allegedly discovered with the help of AI.

Apple, likewise, stated that an internal update to their systems caused their outage.

Major banks experienced technical issues, with Chase stating that a “software bug” on some hardware systems was to blame. The problem may have spread through Zelle, an integration most banks today espouse.

While all of that was happening, NASDAQ dropped 10% this week, and it was likely one of Wall Street’s worst weeks in a while.

But why?

With the launch of Anthropic’s IPO at $83 per share, the company sold 980 million shares which raised over $80 billion. On top of that, Anthropic received a $26 billion investment from major tech companies, including NVIDIA, bringing the total money raised to over $107 billion.

And then there’s NVIDIA, which saw both the ousting of its CEO, Jensen Huang, and a remarkable Q3 result that obliterated expectations with a reported revenue of $115.8 billion. So, Mr. Huang resigned after news of his extramarital affairs became public, with one woman suspected of being a Chinese spy. Yet, even with the massive third quarter gains, the stock fell anyway.

But here’s the thing: NVIDIA is knee-deep in the AI industry, which makes us wonder about the interconnectedness of these seemingly disparate events. Our social feeds shouted everything from “AI Bust” to “Cyber Attacks,” while the official narratives often seemed a little too tidy. No one is admitting that these random events resulted from cyber attacks, and maybe that’s true.

Then, on Friday, November 13th, the FBI issued FLASH-20261113-01, a warning regarding ARTEX, a weaponized AI tool. ARTEX is an open-source, LLM-driven autonomous penetration testing framework, which was originally published to Github in July 2026 as a pentesting tool. The developer name associated with the tool on Github is “Autumn-27”.

The FBI’s warning indicates that the tool has since been weaponized by threat-actors who use it to automate multiple phases of cyber intrusions at machine speed. That is, an AI agent chains together operations like reconnaissance, exploitation, and privilege escalation, all without human involvement.

Sure, it is possible that all of this week’s upgrades, updates, and security patches are in no way related to the events surrounding ARTEX; but given the timing, it’s a challenge not to conflate these things together.

We are accountability journalists. We take what is happening in the world, specifically as it relates to the federal government of the United States, and then we evaluate that information against what the government itself says.

Now, if you’ve read more than a couple of articles on Bureaucracy Times, you are well aware that we do not trust everything we read in every report. We’re not fanboys.

But, we have worked around the government long enough to know that what the government says, what the government does, and what the government says it does, are not always the same.

So, stay frosty, and remember: Don’t trust, verify.

This Week’s Most-Read

The numbers are in. Here’s what you were reading this week:

  1. Seventy Senators Close Debate on a Permitting Bill
  2. State Department Failed to Explain Legal Exemptions
  3. DOT Targets Decades-Old LNG Red Tape
  4. The 20-Minute War at 18,000 Feet
  5. Veterans Questioned Their GI Bill Payments

From the Investigative Desk

GAO Can Tell Congress What FEMA Needs to Fix. Can It Tell the Public?

An oversight report can perform several functions. It can identify a government failure, document corrective action, provide Congress with evidence, and give the public an opportunity to assess whether the agency responsible is doing its job. Sometimes those functions come into conflict.

Our latest restricted-report investigation concerns the Government Accountability Office’s examination of FEMA continuity-of-operations capabilities.

The report, GAO-27-108828SU, was issued November 16 under the title Continuity of Operations: FEMA Has Updated Guidance and Training, but Should Better Monitor Agency Capabilities.

Even that title tells us something worth investigating.

FEMA has apparently updated aspects of its continuity guidance and training, but GAO identified shortcomings in how agency capabilities are monitored. What those shortcomings involve, how serious they are, and what recommendations GAO made cannot be established from the title alone.

That is precisely why we requested the report.

The investigation began November 17 with a formal request for a releasable version under GAO’s public-records regulations, 4 C.F.R. Part 81, rather than FOIA. GAO is a legislative-branch agency, so the distinction is more than administrative trivia.

We did not demand that GAO disclose sensitive emergency procedures or security vulnerabilities. We sought a version that could be released with appropriate redactions.

GAO acknowledged the request the following day, assigning the identification number PRI-27-068 to our request.

The denial arrived by November 20.

GAO cited its public-records regulations and the report’s controlled-unclassified-information status. It also indicated that no public version was planned for future release.

The result raises a broader question about how restricted oversight reports are handled.

GAO frequently publishes reports documenting deficiencies in federal emergency management, information security, acquisition and agency operations. Some necessarily contain sensitive information. But restricting operational details and withholding every substantive finding are not automatically the same decision.

We want to understand whether GAO considered segregating releasable information, whether FEMA participated in the disclosure determination, and what standards govern the decision not to prepare a public version.

Those questions are especially relevant because the report concerns continuity of government operations.

FEMA’s continuity responsibilities are intended to help agencies maintain essential functions during emergencies and other disruptions. Public confidence in that work depends partly on evidence that weaknesses are being identified and corrected.

At the same time, publishing detailed operational vulnerabilities could create risks of its own.

Both considerations are legitimate, but neither eliminates the need for a defensible disclosure process.

This investigation also has a history. Earlier this month, GAO denied two other restricted-report requests, PRI-26-286 and PRI-27-032, citing controlled unclassified information. Those denials prompted us to examine the agency’s Part 81 procedures more closely.

The FEMA denial is therefore not an isolated frustration. It is another opportunity to understand how GAO applies its disclosure rules across different categories of restricted oversight work.

We have not established that GAO improperly classified or withheld the FEMA report. We have not established that the underlying findings reveal a serious undisclosed vulnerability. And we certainly cannot claim to know the report’s conclusions without reading it.

The immediate investigation concerns access to the evidence, not speculation about what the evidence might contain.

On November 20, we sent a procedural inquiry asking how an administrative appeal should be submitted electronically. The regulations provide for an appeal to the Comptroller General, but the correspondence did not resolve every practical filing question.

The 60-day appeal period makes it important to establish the proper procedure promptly.

Our next step is to obtain that clarification, preserve the appeal deadline, and prepare a narrowly reasoned challenge focused on whether a reasonably segregable public version can be provided.

If GAO maintains its denial, we will evaluate what additional public records, congressional materials or agency responses might illuminate the underlying continuity issues without relying on the restricted report.

There is a useful distinction here between the government’s ability to protect genuinely sensitive information and its responsibility to explain how public institutions are performing. The two objectives need not be mutually exclusive.

The public does not need a map of every emergency command facility to understand whether FEMA is adequately monitoring continuity capabilities. It does need enough information to know whether the government has identified problems, assigned responsibility for correcting them, and established a way to measure progress.

That is the accountability question we intend to pursue.

For now, the government’s watchdog has produced a report about whether federal agencies can keep operating during a disruption. Our immediate challenge is getting the watchdog to explain why the public cannot read what it found.

What we’re trying to answer: Can GAO provide a reasonably segregable public version of GAO-27-108828SU, and if not, what standard governs that decision?

FOIA Watch

Another week of federal records work, and another reminder that a document can exist, be cited by its own government, and still remain unavailable to the people who paid for it.

The U.S. Arctic Research Commission finally supplied a completion window. It extends into 2027.
Our longstanding records inquiry, USARC-260906, received a meaningful status update on November 18. The request concerns records associated with the U.S. Arctic Research Commission’s biennial goals and related administrative decisions. The USARC now places the request on its complex processing track, with an estimated completion window of February 19 through March 5, 2027. That is not a disclosure determination. It does, however, replace an indefinite wait with a measurable expectation. The next useful checkpoint will be whether the agency maintains its estimate.

CMS’s Marketplace records inquiries are still accumulating paperwork.
Our inventory review confirmed several pending formal FOIA matters: FY26-44633, FY26-44865, and FY26-44866. A related HHS request, 2027-HHS-FOIA-000160, also remains part of the active records workload. These requests support our examination of enrollment verification, duplicate records and federal payment controls relating to the U.S. Centers for Medicare & Medicaid Services. The underlying policy framework includes the CMS Exchange Pre-Eligibility Verification proposed rule, CMS-9873-P. No new substantive production or final determination was confirmed during November 14–20.

A separate IRS inquiry is testing whether an accounting workaround has become permanent.
On November 16, we sent the IRS a media inquiry arising from GAO’s fiscal 2026 financial audit, GAO-27-108909. The audit gave the IRS an unmodified opinion while identifying a continuing significant deficiency in controls over unpaid tax assessments. IRS recorded approximately $29.8 billion in summary-level corrective adjustments to address classification errors. Our inquiry concerns the status of improvements to the agency’s accounting systems and the timetable for corrective work. The requested response deadline is November 23 at 5 p.m. Eastern.

The filing cabinets remain undefeated. This week, however, one of them finally provided a date. Unfortunately, the date is in February.

On Our Radar

A few things that haven’t become stories. Yet.

Interior has not produced its required coal-reclamation report since 2020.
The GAO examination of coal mine reclamation, GAO-27-107499, publicly released November 12, found that the Office of Surface Mining Reclamation and Enforcement (OSMRE) has not issued its statutorily required nationwide annual performance report since 2020. GAO also found that the agency lacks adequate measures for determining how long inactive mines take to complete reclamation. Interior provided a statement November 16 indicating OSMRE was reviewing the findings without establishing a publication date or a corrective-action schedule. We followed up November 17. We are watching for an actual publication timetable and evidence that the agency can measure reclamation progress consistently.

Seventeen federal agencies have incomplete zero-trust cybersecurity plans.
GAO-27-108661, released November 18, found that only five of 22 reviewed civilian agencies had fully addressed selected federal guidance in their zero-trust implementation plans. On November 19, we initiated targeted inquiries to Commerce, Interior, HHS and OMB. The agencies have been asked to respond by November 25. GAO’s findings do not mean 17 agencies have no cybersecurity protections. They mean their planning does not fully address the selected guidance GAO evaluated. That distinction deserves to survive the headline.

The IRS has a clean audit opinion and a persistent $29.8 billion accounting adjustment.
The IRS fiscal 2026 financial audit concluded that the agency’s financial statements were fairly presented in all material respects — while documenting persistent weaknesses in systems used to classify and account for unpaid assessments. The approximately $29.8 billion in corrective adjustments reflects classification errors in the underlying data, not a newly discovered loss of tax revenue. Our November 16 media inquiry asks what progress the IRS has made and whether the agency has a credible implementation timetable.

Sign-off

We’ve learned a lot this week, and yet we’re more befuddled than ever. When we sit around to discuss these topics each week, there are always moments of bewilderment. That is, with all jokes aside, the government in a nutshell.

There is no perfect government, and there never will be while we humans run the show. Our human nature prevents the very utopia many people dream of and political leaders promise.

Even so, we prefer governance and feigned civility to lawlessness and anarchy. More than anything, though, we seek the truth in all things. So don’t be afraid to ask questions, and certainly don’t trust information until you verify whether or not it’s true.

Until next week —

hannotek, Editor @ Bureaucracy.News

Editorial note: This edition covers November 14–20, 2026. Linked GAO reports and federal regulations were verified against public sources. The FEMA restricted report, Army Reserve correspondence, and several FOIA acknowledgments have no verified public document URLs; those limitations are identified in the text. Internal Bureaucracy Times article URLs were not independently verified and have not been invented.


Advertisements

Discover more from Bureaucracy Times

Subscribe to get the latest posts sent to your email.