30
30
30
30
55
The Rise of the Forward Deployed Engineer — and How To Do the Job Right
Palantir veteran Vinoo Ganesh traces the forward deployed engineer role and shares practices for building effective FDE teams.
Kepler CEO and former Palantir forward deployed engineer Vinoo Ganesh argues that labs, startups, and PE firms hire FDEs without a shared definition of the role. He recounts Palantir's Project Frontline rotation, which trained about 250 software engineers as FDEs, many now leading forward deployed teams at OpenAI, Anthropic, xAI, and Anduril. A 2013 failure of the Phoenix transaction store at a bank, where real-world data gaps caused roughly 2.3 million keyspaces and an out-of-memory crash, illustrates why FDEs must own the gap between design and production reality. At Kepler he places the FDE function inside product rather than sales.
30
30
You're deploying it wrong! TeamCity, Subversion & Web Deploy part 2: MSBuild and deployable packages
30
42
Top 10 Best Patch Management Software in 2026
Roundup ranks 2026 patch management software, favoring Automox, Action1's free tier and Tanium, and warns buyers to vet patching platform security.
This buyer's guide ranks ten patch management tools for 2026, placing Automox first for cloud-native patching, Action1 for a genuinely free small-estate tier and Tanium for patching hundreds of thousands of endpoints. It contextualizes the category with the 2021 Kaseya VSA ransomware supply-chain incident and the 2020 SolarWinds Orion compromise, arguing the security of the patching platform itself must be part of evaluation. It also notes Ivanti products have repeatedly appeared in CISA's Known Exploited Vulnerabilities catalog.
14
Threat Matrix: Mapping threats across cloud web applications
Microsoft released a Cloud Web Applications Threat Matrix, a MITRE ATT&CK-aligned framework mapping threats to cloud-hosted web apps and serverless platforms.
Microsoft introduced the cloud web applications threat matrix, which organizes attack techniques for cloud-hosted web apps and serverless platforms using MITRE ATT&CK tactics, from resource development through impact. The framework covers attack paths spanning application code, managed runtimes, workload identities, and deployment pipelines, cataloging techniques such as subdomain takeover, code injection in connected repositories, compromised registry images, exposed admin interfaces, and serverless trigger injection. It builds on Microsoft's earlier Kubernetes and storage services matrices to help defenders identify visibility gaps, prioritize hardening, and plan investigations in cloud-native environments.
35
30
30
30
You're deploying it wrong! TeamCity, Subversion & Web Deploy part 4: Continuous builds with TeamCity
30
42
42
47
60
30
30
Threat Assessment: Ryuk Ransomware
Unit 42 assesses Ryuk ransomware amid a CISA/FBI/HHS alert on threats to U.S. healthcare, including the UHS attack that disrupted hospital operations.
A joint CISA, FBI, and HHS alert on October 28, 2020 warned of an imminent threat to U.S. healthcare from operators deploying Trickbot and Ryuk ransomware. Universal Health Services reported a Ryuk attack that disrupted all U.S. UHS sites for weeks, with similar incidents at hospitals in Oregon and New York. Ryuk typically arrives after Trickbot or BazaLoader infections delivered via malicious email, and operators enumerate networks with PowerShell and WMI before encryption. The Trickbot Anchor_DNS module performs DNS tunneling for C2, using connectivity checks to benign domains like ipinfo.io and checkip.amazonaws.com.
68
55
47
30
30
45
30
Why Patch Automation Needs Brakes, Not Just an Accelerator
Action1's field CTO argues patch automation needs staged deployments and stop conditions, not just speed.
Gene Moody, Field CTO at Action1, writes on BleepingComputer that patch automation must pair acceleration with safeguards. He recommends staged deployment rings with predefined go/no-go criteria, keeping human judgment for domain controllers, databases, and ERP systems. The piece warns that automation without brakes can push a bad update to 10,000 endpoints as fast as a good one.
12
AI deployments are stretching enterprise security to its limits
NetFoundry survey finds AI deployments will expand enterprise attack surfaces by 14%, with 90% of leaders worried about unapproved employee AI use.
NetFoundry's 2026 State of Secure AI Access survey found CISOs and CTOs expect AI deployments to grow attack surfaces by an average 14% within a year, with 90% concerned about employees using unapproved AI tools. Only 15% expressed high confidence that existing tools protect AI deployments, while non-human identities, static credentials and internet-facing APIs drive risk, and vulnerability exploitation now accounts for about 31% of breaches. Security reviews and network changes add an average eight days to AI deployments, and the median time to patch known exploited vulnerabilities has risen to 43 days.
35
42
42
30
30
55
60
60
30
60
55