home.social

#kaseya — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #kaseya, aggregated by home.social.

  1. Nachdem es in den letzten Jahren Angriffe auf #Solarwinds oder #Kaseya gab, steht immer stärker auch die #Opensource Community im Fokus von #Cybercrime, indem durch die Kompromittierung einer Maintainer-Identität potenziell Millionen von Entwicklungsumgebungen und CI/CD-Pipelines ebenfalls kompromittiert werden.

    So haben haben Angreifer die #JavaScript-Bibliothek #Axios, eine der meistgenutzten Komponenten moderner Webentwicklung, zeitweise mit #Schadsoftware bestückt:

    it-daily.net/shortnews/npm-bib

  2. New by me: I’ve been seeing a spike in unwanted apps (PUPs/adware) sneaking onto client endpoints, so I built a practical workaround when allowlisting tools aren’t in the budget.

    This post walks through:
    ✅ a PowerShell cleanup script (Audit vs Remediate)
    ✅ a JSON “bad app” list you can update over time
    ✅ how to automate it in your RMM (with a Kaseya VSA X example)
    ✅ why I avoid Win32_Product and how the fallback config works

    MSPs: this is endpoint hygiene, not magic, but it’s consistent and scalable.

    kylereddoch.me/blog/fighting-t

    #MSP #PowerShell #RMM #Windows #Cybersecurity #EndpointSecurity #Kaseya

  3. New by me: I’ve been seeing a spike in unwanted apps (PUPs/adware) sneaking onto client endpoints, so I built a practical workaround when allowlisting tools aren’t in the budget.

    This post walks through:
    ✅ a PowerShell cleanup script (Audit vs Remediate)
    ✅ a JSON “bad app” list you can update over time
    ✅ how to automate it in your RMM (with a Kaseya VSA X example)
    ✅ why I avoid Win32_Product and how the fallback config works

    MSPs: this is endpoint hygiene, not magic, but it’s consistent and scalable.

    kylereddoch.me/blog/fighting-t

    #MSP #PowerShell #RMM #Windows #Cybersecurity #EndpointSecurity #Kaseya

  4. New by me: I’ve been seeing a spike in unwanted apps (PUPs/adware) sneaking onto client endpoints, so I built a practical workaround when allowlisting tools aren’t in the budget.

    This post walks through:
    ✅ a PowerShell cleanup script (Audit vs Remediate)
    ✅ a JSON “bad app” list you can update over time
    ✅ how to automate it in your RMM (with a Kaseya VSA X example)
    ✅ why I avoid Win32_Product and how the fallback config works

    MSPs: this is endpoint hygiene, not magic, but it’s consistent and scalable.

    kylereddoch.me/blog/fighting-t

    #MSP #PowerShell #RMM #Windows #Cybersecurity #EndpointSecurity #Kaseya

  5. New by me: I’ve been seeing a spike in unwanted apps (PUPs/adware) sneaking onto client endpoints, so I built a practical workaround when allowlisting tools aren’t in the budget.

    This post walks through:
    ✅ a PowerShell cleanup script (Audit vs Remediate)
    ✅ a JSON “bad app” list you can update over time
    ✅ how to automate it in your RMM (with a Kaseya VSA X example)
    ✅ why I avoid Win32_Product and how the fallback config works

    MSPs: this is endpoint hygiene, not magic, but it’s consistent and scalable.

    kylereddoch.me/blog/fighting-t

    #MSP #PowerShell #RMM #Windows #Cybersecurity #EndpointSecurity #Kaseya

  6. New by me: I’ve been seeing a spike in unwanted apps (PUPs/adware) sneaking onto client endpoints, so I built a practical workaround when allowlisting tools aren’t in the budget.

    This post walks through:
    ✅ a PowerShell cleanup script (Audit vs Remediate)
    ✅ a JSON “bad app” list you can update over time
    ✅ how to automate it in your RMM (with a Kaseya VSA X example)
    ✅ why I avoid Win32_Product and how the fallback config works

    MSPs: this is endpoint hygiene, not magic, but it’s consistent and scalable.

    kylereddoch.me/blog/fighting-t

    #MSP #PowerShell #RMM #Windows #Cybersecurity #EndpointSecurity #Kaseya

  7. What Is a Supply Chain Attack? Lessons from Recent Incidents

    924 words, 5 minutes read time.

    I’ve been in computer programming with a vested interest in Cybersecurity long enough to know that your most dangerous threats rarely come through the obvious channels. It’s not always a hacker pounding at your firewall or a phishing email landing in an inbox. Sometimes, the breach comes quietly through the vendors, service providers, and software updates you rely on every day. That’s the harsh reality of supply chain attacks. These incidents exploit trust, infiltrating organizations by targeting upstream partners or seemingly benign components. They’re not theoretical—they’re real, costly, and increasingly sophisticated. In this article, I’m going to break down what supply chain attacks are, examine lessons from high-profile incidents, and share actionable insights for SOC analysts, CISOs, and anyone responsible for protecting enterprise assets.

    Understanding Supply Chain Attacks: How Trusted Vendors Can Be Threat Vectors

    A supply chain attack occurs when a threat actor compromises an organization through a third party, whether that’s a software vendor, cloud provider, managed service provider, or even a hardware supplier. The key distinction from conventional attacks is that the adversary leverages trust relationships. Your defenses often treat trusted partners as safe zones, which makes these attacks particularly insidious. The infamous SolarWinds breach in 2020 is a perfect example. Hackers injected malicious code into an update of the Orion platform, and thousands of organizations unknowingly installed the compromised software. From the perspective of a SOC analyst, it’s a nightmare scenario: alerts may look normal, endpoints behave according to expectation, and yet an attacker has already bypassed perimeter defenses. Supply chain compromises come in many forms: software updates carrying hidden malware, tampered firmware or hardware, and cloud or SaaS services used as stepping stones for broader attacks. The lesson here is brutal but simple: every external dependency is a potential attack vector, and assuming trust without verification is a vulnerability in itself.

    Lessons from Real-World Supply Chain Attacks

    History has provided some of the most instructive lessons in this area, and the pain was often widespread. The NotPetya attack in 2017 masqueraded as a routine software update for a Ukrainian accounting package but quickly spread globally, leaving a trail of destruction across multiple sectors. It was not a random incident—it was a strategic strike exploiting the implicit trust organizations placed in a single provider. Then came Kaseya in 2021, where attackers leveraged a managed service provider to distribute ransomware to hundreds of businesses in a single stroke. The compromise of one MSP cascaded through client systems, illustrating that upstream vulnerabilities can multiply downstream consequences exponentially. Even smaller incidents, such as a compromised open-source library or a misconfigured cloud service, can serve as a launchpad for attackers. What these incidents have in common is efficiency, stealth, and scale. Attackers increasingly prefer the supply chain route because it requires fewer direct compromises while yielding enormous operational impact. For anyone working in a SOC, these cases underscore the need to monitor not just your environment but the upstream components that support it, as blind trust can be fatal.

    Mitigating Supply Chain Risk: Visibility, Zero Trust, and Preparedness

    Mitigating supply chain risk requires a proactive, multifaceted approach. The first step is visibility—knowing exactly what software, services, and hardware your organization depends on. You cannot defend what you cannot see. Mapping these dependencies allows you to understand which systems are critical and which could serve as entry points for attackers. Second, you need to enforce Zero Trust principles. Even trusted vendors should have segmented access and stringent authentication. Multi-factor authentication, network segmentation, and least-privilege policies reduce the potential blast radius if a compromise occurs. Threat hunting also becomes crucial, as anomalies from trusted sources are often the first signs of a breach. Beyond technical controls, preparation is equally important. Tabletop exercises, updated incident response plans, and comprehensive logging equip teams to react swiftly when compromise is detected. For CISOs, it also means communicating supply chain risk clearly to executives and boards. Stakeholders must understand that absolute prevention is impossible, and resilience—rapid detection, containment, and recovery—is the only realistic safeguard.

    The Strategic Imperative: Assume Breach and Build Resilience

    The reality of supply chain attacks is unavoidable: organizations are connected in complex webs, and attackers exploit these dependencies with increasing sophistication. The lessons are clear: maintain visibility over your entire ecosystem, enforce Zero Trust rigorously, hunt for subtle anomalies, and prepare incident response plans that include upstream components. These attacks are not hypothetical scenarios—they are the evolving face of cybersecurity threats, capable of causing widespread disruption. Supply chain security is not a checkbox or a one-time audit; it is a mindset that prioritizes vigilance, resilience, and strategic thinking. By assuming breach, questioning trust, and actively monitoring both internal and upstream environments, security teams can turn potential vulnerabilities into manageable risks. The stakes are high, but so are the rewards for those who approach supply chain security with discipline, foresight, and a relentless commitment to defense.

    Call to Action

    If this breakdown helped you think a little clearer about the threats out there, don’t just click away. Subscribe for more no-nonsense security insights, drop a comment with your thoughts or questions, or reach out if there’s a topic you want me to tackle next. Stay sharp out there.

    D. Bryan King

    Sources

    Disclaimer:

    The views and opinions expressed in this post are solely those of the author. The information provided is based on personal research, experience, and understanding of the subject matter at the time of writing. Readers should consult relevant experts or authorities for specific guidance related to their unique situations.

    Related Posts

    Rate this:

    #anomalyDetection #attackVector #breachDetection #breachResponse #CISO #cloudSecurity #cyberattackLessons #cybersecurity #cybersecurityGovernance #cybersecurityIncident #cybersecurityMindset #cybersecurityPreparedness #cybersecurityResilience #cybersecurityStrategy #EndpointSecurity #enterpriseRiskManagement #enterpriseSecurity #hardwareCompromise #hardwareSecurity #incidentResponse #incidentResponsePlan #ITRiskManagement #ITSecurityPosture #ITSecurityStrategy #Kaseya #maliciousUpdate #MFASecurity #MSPSecurity #networkSegmentation #NotPetya #organizationalSecurity #perimeterBypass #ransomware #riskAssessment #SaaSRisk #securityAudit #securityControls #SOCAnalyst #SOCBestPractices #SOCOperations #softwareSecurity #softwareSupplyChain #softwareUpdateThreat #SolarWinds #supplyChainAttack #supplyChainMitigation #supplyChainRisk #supplyChainSecurityFramework #supplyChainVulnerabilities #thirdPartyCompromise #threatHunting #threatLandscape #trustedVendorAttack #upstreamCompromise #upstreamMonitoring #vendorDependency #vendorRiskManagement #vendorSecurity #vendorTrust #zeroTrust

  8. 🎯 NOW PUBLISHING: On-Location Coverage from #BlackHat USA 2025!

    We're back in the office and excited to start sharing all the conversations we captured on location in Las Vegas with our amazing sponsors and editorial coverage!

    🔔 Follow ITSPmagazine, Sean Martin, CISSP, and Marco Ciappelli to get this content fresh as it drops!

    We're thrilled to share this critical Brand Story conversation thanks to our friends at ReversingLabs 🙏

    Your Business Apps Are Bringing Friends You Didn't Invite

    Every commercial software application is a complex assembly of first-party, contracted, open source, and third-party code. But when #SolarWinds, #Kaseya, and #Ivanti happened, we learned that vendor questionnaires and contractual assurances offer little protection against supply chain compromises.

    At #BlackHat2025, Saša Zdjelar, Chief Trust Officer at ReversingLabs, reveals how organizations can finally verify the integrity of #software from outside vendors—without relying on blind trust.

    The game-changer: Comprehensive binary analysis that deconstructs any file into its components to:

    • Detect malware, tampering, and embedded secrets

    • Identify #vulnerabilities and insecure practices

    • Uncover undocumented network connections

    • Flag #compliance risks from restricted regions

    This isn't just another policy checkbox—it's a true technical control that inspects the software itself, regardless of size or complexity.

    Real-world applications:

    • Procurement: Auto-scan all software before deployment

    • Version Monitoring: Detect unexpected behavior changes between releases

    • Critical Environments: Verify integrity before software enters OT, ICS, or financial systems

    • Risk Management: Assess COTS software as part of ongoing vendor reviews

    With regulations like EO 14028 and the EU's #CyberResilience Act demanding transparency, the ability to technically validate every application delivers both strategic protection and measurable benefits.

    📺 Watch the video: youtu.be/pU9bHYFND7c

    🎧 Listen to the podcast: brand-stories-podcast.simpleca

    📖 Read the blog: itspmagazine.com/their-stories

    ➤ Learn more about ReversingLabs: itspm.ag/reversinglabs-v57b

    ✦ Catch more stories from #ReversingLabs: itspmagazine.com/directory/rev

    🎪 Follow all of our #BHUSA 2025 coverage: itspmagazine.com/bhusa25

    #Cybersecurity #SupplyChainSecurity #SoftwareIntegrity #BlackHatUSA #BHUSA25 #ThirdPartyRisk #SBOM #BinaryAnalysis #Compliance #ZeroTrust

  9. “This will enhance our security posture across the board while also helping MSPs and their customers meet requirements like FEDRamp and CMMC,”

    mspsuccess.com/2025/02/kaseya-

    #kaseya #msps #fedramp

  10. If any uses #Kaseya, do you know if the cloud version of VSAX is down?

    #VSAX #RMM #MSP

  11. It’s getting real now. #KaseyaConnect24 Conference registration has been completed!

    Can the last week of April come any sooner?

    #Kaseya #Conference #MSP #IT #Vegas

  12. Today ended up being quite the busy day. Man!

    Repurposed and old ass Dell Optiplex into an Ubuntu machine. Ran some stress tests on this low end gaming machine this guy says is running slow (Lol). All while getting my Kaseya Certified Administrator in VSAX certification.

    I’m tired.

    #Busy #WhatADay #Ubuntu #Kaseya #VSAX #IT #RMM

  13. When you are going through a Quick Guide for an integration and the steps...DON'T WORK, that is the most frustrating thing!!!

    #Kaseya #VSA #ComplianceManagerGRC #WorkProblems #Frustration #WorkIssues

  14. Throwing this out again.

    Anyone on the #Fedierse use any #Kaseya products/services? I would like to connect!

    #IT #MSP

  15. Anyone on here work with the #Kaseya software/systems? I am looking to connect with ones that do.

    #MSPs #IT #VOIP #PSA #CRM

  16. Die Unitrend Recovery und Agents-Produktreihen von Kaseya enthalten Schwachstellen, durch die Angreifer beliebigen Code einschleusen und ausführen könnten.
    Kaseya schließt teils kritische Sicherheitslücken in Unitrend Backup
  17. The Justice Department announced actions taken against two foreign nationals charged with deploying Sodinokibi/#REvil ransomware to attack businesses and government entities in the U.S. An indictment charges Yaroslav Vasinskyi, 22, a Ukrainian national, with conducting #ransomware attacks against multiple victims, including the July 2021 attack against #Kaseya, a multi-national information #technology #software company. #europe #usa #cyber #police #justice #informatique

    youtube.com/watch?v=MJvZD6ABAZ

  18. kurz informiert liefert täglich die wichtigsten Nachrichten zu IT, Mobilem, Gadgets, Netzpolitik & Wissenschaft.
    Kurz informiert: Kaseya, Bot-Attacken, Babbel, Ebay
  19. Nachdem der IT-Dienstleiter Kaseya Opfer einer perfiden Attacke geworden war, wurde es für die Opfer teuer. Das FBI hielt derweil einen Generalschlüssel zurück.
    Kaseya-Attacke: FBI hielt wochenlang Generalschlüssel zurück
  20. Die Gang, deren Kaseya-Lieferkettenangriff Schlagzeilen machte, war Mitte Juli von der Bildfläche verschwunden – nun ist ihre Tor-Onion-Leak-Site wieder aktiv.
    Ransomware: Erpressungs-Website der "REvil"-Gang plötzlich wieder online