
Founder (@jbc_sec) | IT/Cyber Architect | Author ▶️ https://xitter.cf/t.co/tQe0lylvuo Maine born🦞 | Husband and Father USAF UMUC JHU
Sign up for my IT/Cyber blog👍
Joined May 2018
- Tweets70.7K
- Following774
- Followers31.7K
- Likes119K
Don't spend that cash just yet when looking for IT learning resources, give my YouTube channel a look first…
🛜Networking (Net+, Cisco, Juniper)
🔎Cyber (Red,Blue,GRC)
☁️Cloud (AWS, Azure, Cloud Security)
🐧Linux/Windows
🛠️Hands-on Labs
📝Cert Practice Test Walkthroughs
📑Exam Reviews
💰Career Advice
youtube.com/c/cyberinsight
I always really enjoy the in-depth discussions from @techspence @merill and @IAMERICAbooted. As a consultant/architect with a stronger background on the networking/GRC/AWS side of things than Microsoft, it's always enlightening to hear sides that challenge what I have done in the past or previously understood.
When it comes to this discussion on keeping end-user devices off AD, does this diagram I threw together kind of encompass the main design points?
Replying to @techspence @WellKnitTech
It absolutely does. I was just like you. There is always a way to domain admin.
Nobody ever said don't protect your endpoints if you're not in the cloud. You protect them the same way you do if they are hybrid joined, just using a different technology.
I helped build a cloud native org. We implemented STIGs on all our endpoints. They all had the slew of security point solutions too: SASE, EDR, Endpoint DLP, Insider Threat, ASR, etc.
What I'm talking about has nothing to do with Entra. It's about moving employee devices out of AD to reduce attack surface because they don't need to be there and it reduces an incredible amount of attack surface. This has been a recommended best practice for a couple years now since Secure Future Initiative.
Let me ask you something: How many times have you gotten domain admin or global admin from a device that was unable to talk to Active Directory?
Active Directory is legacy and highly insecure in every organization I've consulted with.
I thought security people were supposed to help people get off legacy and follow documented best practices?
The reality with configuration based security improvements on-prem is not just that they are expensive. It's that the CIA triad includes availability and pentesters don't appreciate the services that get taken down in Sev1 and Sev2 incidents or degraded when you have to try to fix things on-prem. It's easy to say in a report, much harder to achieve in reality when the business requires you to be available all the time with no issues because that service that might be affected makes the company a million dollars a day.
Why would the security community at all be advocating for increased attack surface? Access to shares, mapped drives, and NAS don't require domain admin for atatckers to smash and grab. Access to databases often leads to privilege escalation and ability to exfil from tier 2. If Tier 2 should be treated as hostile, why not remove it? Again, it's a documented best practice.
I, like you, got domain admin on every engagement except one (because they didn't want me to). How often was I able to achieve that from a cloud only device? Just a couple times. It's significantly harder to compromise a global admin in that scenario unless you phish them directly or land on a device in a privileged role.
John Breth (JB) | CyberInsight® on YouTube retweeted
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.
Sometimes you just want buffalo chicken dip for dinner 😂 #boydinner
Replying to @codisfy @MagicalTux
Potentially as simple as putting this into the php.ini :
session.upload_progress.enabled = Off
Will stop it from processing uploads in any arbitrary php file even if it doesn't process uploads...see my other post or this one :
xitter.cf/J4ck3LSyN/status/21127…
This quoted post is unavailable.
Michael Rapaport is by far my favorite person on any season of Traitors. I wish he could be on every season 😂
John Breth (JB) | CyberInsight® on YouTube retweeted
Full details of a remotely exploitable vulnerability in the core engine of *all* PHP versions will be released tomorrow, October 21st. If your organization has internet facing PHP applications then you need to be ready to patch the minute the update is released or *strongly* consider taking the application offline until you can:
php.net/index.php#2026-10-20…
🚨 PHP warns of two critical vulnerabilities as emergency patches arrive tomorrow
The PHP security team will release updates on October 21 at 14:00 UTC for two vulnerabilities, each rated 9.2 under CVSS v4.0.
⠀
Security researchers identified the flaws as CVE-2026-109618 and CVE-2026-109619 and described them as remote code execution vulnerabilities reportedly affecting PHP versions 5 through 8.
PHP has not yet confirmed the affected versions, exploitation requirements or fixed releases.
⠀
The vulnerabilities were reportedly leaked before their planned disclosure. Researchers said they have not observed active exploitation, while PHP warned it may release the patches early if technical details become public or exploitation is detected.
⠀
Administrators should identify PHP installations now and prepare to apply the updates as soon as they become available.
John Breth (JB) | CyberInsight® on YouTube retweeted
didn't the patriots medical staff immediately shut down christian barmore for an entire season because of a similar thing?
John Breth (JB) | CyberInsight® on YouTube retweeted
Me and my mom were talking about trips to take next year. Somehow lobster rolls, then Maine got mentioned. and she gasped because she said she’s always wanted to go but never thought anybody else would want to.
It’s your time to shine @JBizzle703 😭





















