Matthew Engler retweeted
Cybersecurity is arguably the best career path in all of tech.
It's in demand no matter what the job market looks like. There are always more openings than candidates.
Now AI is writing the attacks too, and breaches are way too expensive to ignore.
The F500s are about to pour even more money into security.
BREAKING: Google says “the era of autonomous attacks has arrived.”
Hackers are now using AI to scan software updates, figure out which security flaw each patch fixes and build an attack before companies can install the fix, all without a human involved, according to a new report from the Google Threat Intelligence Group.
“Defending against machine-speed threats at human speed isn’t feasible,” Google said.
The House passed bipartisan cyber bills, which would require @SBAgov to provide cybersecurity and CMMC compliance guidance and help small businesses guard against threats from foreign adversaries. meritalk.pulse.ly/cb6rx17vsn
Matthew Engler retweeted
Barracks Task Force Senior Advisor Dakota Meyer says military leaders have less than a week to move any service member living in emergency conditions in unaccompanied housing. militarytimes.com/video/2026…
Matthew Engler retweeted
I love the story he shared on @ShawnRyan762 about the creation of the DAP
They got some stencils from Walmart and drew it out on paper
On October 3, 1993, Chief Warrant Officer Mike Durant was flying Super 64, an MH-60 Black Hawk with the 160th SOAR, when an RPG hit the tail rotor over Mogadishu.
The aircraft crashed, killing crewmates Bill Cleveland, Ray Frank, and Tommy Field. Durant was badly hurt, a broken back and a compound fracture of the femur, and Delta Force snipers Gary Gordon and Randy Shughart were killed trying to hold the site.
He was the only American taken alive that day, held for 11 days before his release. He retired in 2001 as a CW4 and Master Aviator after 22 years that also included Just Cause and Desert Storm.
After the Army he wrote In the Company of Heroes, built Pinnacle Solutions in Huntsville into a defense training firm, and later ran in the 2022 Republican primary for US Senate in Alabama.
33 years later, his story is still less about one pilot’s survival than about the people who did not come home with him.
"Night Stalkers Don't Quit"
Matthew Engler retweeted
In WWII, the Office of Strategic Services was forged on a defining American truth: when the Nation is tested, Americans rise, endure, and prevail.
The men and women of the OSS went into the night with no promise of safety, no guarantee of return, and no expectation of praise. They went because their country called. They went because the cause was just. They went because Americans do not turn from the hard road when duty points the way.
That legacy lives today in America’s Special Operations Forces. They carry the Nation’s hardest missions into the world’s most dangerous places, often without recognition and always with extraordinary responsibility.
Today, I am pleased to announce that Secretary Hegseth has signed a pivotal memorandum enabling the ASW(SO/LIC) to fully exercise its statutory authority in line with Congress’s intent by elevating the office to Under Secretary of War equivalence and restoring its name to the Office of Strategic Services (OSS).
This action is a pledge that those sent into the hardest places, entrusted with the gravest responsibilities, and called upon when all else has failed will have a voice equal to the burden placed upon their shoulders. They will be given the resources, authority, and support required to prepare, to endure, and to prevail.
In honoring our Special Operators, we honor the courage, sacrifice, and unbreakable American spirit that has carried this Nation through its hardest hours and will carry us forward still.
Read the full release here:
war.gov/News/Releases/Releas…
Matthew Engler retweeted
President Trump has nominated Palantir's CISO to be the next director of CISA. He faces uncertain prospects in the Senate and a daunting task if confirmed. cybersecuritydive.com/news/t…
Matthew Engler retweeted
If you have been selling into the DoW and don't know how the procurement process works or how the ops/planning process works, you clearly don't know the customer
If you don't know the customer you don't know what to build and how to price it. You don't know how to price it because you don't know the details
Matthew Engler retweeted
Since July, our team has had more than 100 calls about AI implementation with CEOs, CFOs, CTOs and PE operating partners.
These 12 questions came up most often:
1. “Where do we start?”
Where your customer would feel it first. Pick one workflow, run it for a month, then decide what comes next. Start with a long list of ideas and you’ll end up shipping none of them.
2. “Can’t we just build this ourselves with Claude?”
For a lot of it, yes. Reports, research, content: get your people using agents every day. You don’t need a firm for that. You need one when the work touches a system of record, patient data or payment data, or when it has to run every day without somebody babysitting it.
3. “How do we measure ROI?”
Name the number before you build: days to close, denial rate, hours per onboarding. If nobody can name it, you’re buying a demo.
4. “How do we know the AI is right?”
You test it. Build a golden set of answers your business agrees are correct, then score every release against it. Anything below the bar goes to a person.
5. “Who owns it, and who keeps it running?”
You do. Your cloud, your repo, your accounts. Before kickoff, name the person on your side who will run it. Make your first AI hire somebody who can operate it and keep it healthy.
6. “Is our data safe?”
It should stay in your environment. Ask where it goes, who at the vendor can see it and what the model provider keeps. Expect a plain answer to all three.
7. “Do we have to fix our data first?”
Only the data your first workflow touches. Then build in order: a simple pipeline that runs every day, a layer that defines what your numbers mean, and then the agent. One prompt can’t do all three.
8. “What happens to our people?”
Start with them. You can’t expect agents to work on top of a team that doesn’t use them.
9. “Which model should we use?”
It matters less than you think, and you’ll change it. Pick a setup that lets you switch. Your workflows, evals and data are what you keep.
10. “What will it cost to run?”
Get it in writing before the build: tokens, hosting and licences, with costs broken down per month and per transaction.
11. “Do we pay for time or for outcomes?”
Either works as long as you can walk away. Work month-to-month, with no lock-in and a checkpoint after the first month.
12. “How do we tell a real AI partner from one that started last year?”
Before you sign, ask to see something they built that’s running in production for another customer today. Then call that customer. After you sign, give them one team for a month. If nothing changed, throw them out.
The question I’d add to the list: what happens if it works?
Who runs it, who improves it, and what does your team do with the time it gives back?
Ask it before you start.
I sat through a virtual interview where I answered questions to no one.
Applied for a GS job not long ago. First round was a self-recording. You sit there and talk to a camera. No one on the other side. It felt off. Curious if anyone else has done one of these and how it landed.
1
2
62
Took me longer than I'd like to admit to get this straight. The ISSO is usually the one in the weeds on a specific system day to day. The ISSM sits over a bunch of systems and the ISSOs. Then there's the system owner, who's on the hook for the whole thing but might never touch a control. Practitioners, did I get that right or is it messier in real life?
3
49
Just signed up for the Eastern Defense Summit in Charleston this December.
It is December 8–10 at the Charleston Area Convention Center. Hosted by the Charleston Defense Contractors Association. The theme this year is collaborating on actionable solutions for pacing threats, from mission need to fielded capability.
Charleston has a strong defense presence (NIWC Atlantic, Joint Base Charleston, and others), and the event has grown fast. Last year had over 2,000 attendees and a sold-out exhibit hall.
If you have been, what was useful? Which conversations or sessions were worth the time, and which ones were easy to skip? Curious what stood out.
1
30
Learned this week that in DoD land one 800-53 control gets broken into a bunch of smaller pieces called CCIs. So a control I thought was one checkbox can turn into ten things somebody has to show evidence for. Explains a lot about why packages get so thick. Practitioners, is that where most of the hours go?
3
23
Took me a minute to get that a STIG and a control aren't the same thing. The control says what has to be true. The STIG tells you exactly how to configure the box so it is. Sounds obvious now, but nobody explained it to me that way at first. Practitioners, which STIG fights you every single time?
1
20
Learned a new one this week. Type authorization. Instead of every site getting its own ATO for the same kit, you authorize the system once and deploy identical copies, and each site just covers its local stuff. Makes total sense on paper. Question for the practitioners: how identical do those copies actually stay after a year in the field?
14
New one for me this week: an ATO with conditions. The system gets to operate, but the AO attaches strings. Fix this by this date or the authorization is in trouble. Sounds simple on paper. For the folks who live this, do the conditions actually get tracked to closure or do they quietly ride along until the next reauthorization?
16
Matthew Engler retweeted
Army Project Gatekeeper opens today. Vendors can upload code to an unclassified environment and get vulnerability and compliance feedback before anything touches an Army network, with no contract required. Logging in takes a CAC until Login(dot)gov access arrives, which the Army is targeting for mid-November.
Source: Federal News Network
Matthew Engler retweeted
The ultimate sales superpower is being able to articulate your buyer's problem better than they can.
Gatekeeper is live.
Acting Army CIO Gabe Chiulli put a stake in the ground on this. Companies can submit code and get a read in minutes instead of waiting months for someone to look at it. That is the right problem to attack.
It solves the front of the line. An authorizing official still has to accept residual risk on a system that has to stay up. A fast scan is real progress. The package still has to hold when someone signs it.
Credit to the team for making the start of the process less of a black box.
defensescoop.com/2026/10/14/…
1
34
Learned something this week I didn't expect. In DoD a system doesn't just get its ATO and go live on its own. It has to be aligned to a Cybersecurity Service Provider, basically the team watching it and responding when something goes sideways. For the ISSOs out there, how early does that conversation actually happen? Sounds like it's often later than it should be.













