Uptycs Blog

Welcome! The Uptycs blog is for security professionals and osquery enthusiasts interested in exploring new ideas in cloud security. We hope you’ll enjoy our blog enough to subscribe and share.

Building Your First Incident Response Policy: A Practical Guide for Beginners

Building Your First Incident Response Policy: A Practical Guide for Beginners

It only makes sense to assume that sooner or later your company will have to handle a security incident and the subsequent recovery from any damage caused.

Creating an incident response policy before an incident occurs can help you minimize risk and ensure that you and your team are prepared. By planning your response ahead of time, you will be able to respond faster and more efficiently, and possibly even prevent additional damage from occurring.

Uptycs & Cortex XSOAR: Orchestrating Incident Response Activities

Uptycs & Cortex XSOAR: Orchestrating Incident Response Activities

Orchestration engines such as Palo Alto Networks Cortex XSOAR give security professionals the freedom to integrate multiple services into coordinated, automated workflows.  Simple REST APIs allow the transfer of data from one application or service to another in a reliable, straight-forward manner. With the appropriate data sources, users are enabled to create workflows and reports for incident investigation and response. In removing the human element, orchestration engines can improve the overall efficiency and consistency of incident response, while freeing up time for other tasks.

Uptycs leverages the open-source osquery agent in order to acquire real-time data about nearly any facet of your infrastructure (more about osquery here). This data is streamed, aggregated, and stored in the Uptycs backend and then made accessible via our API, allowing the integration of Uptycs data with other services.

Hardening defenses with MITRE ATT&CK and osquery: Lessons from Singapore Health breach

Hardening defenses with MITRE ATT&CK and osquery: Lessons from Singapore Health breach

There's a big disconnect between best practice frameworks and the real-life nitty gritty. Many of these frameworks broadly approach the overarching principles that a robust security program should encompass and why these principles are important; however, they don't usually say specifically what kind of attacker behavior a defender should anticipate when building their security programs, nor do they detail how an attacker would work to thwart those vaulted best practices. Often, that's left up to the security practitioner to suss out themselves in their copious spare time.

Detecting malicious packages in repositories like PyPI: Using osquery for complete software inventory

Detecting malicious packages in repositories like PyPI: Using osquery for complete software inventory

Many systems make installing third-party software incredibly convenient; from packaging systems and well loved Linux distribution tools like Debian Apt to app stores and per-language repositories. Users are also often allowed to install browser extensions or plugins, which come from their own “store” and are just another type of software. For these reasons, and without forgetting containers, maintaining a software inventory that allows you to identify dangerous packages has become harder to do, but more critical to accomplish.

[Video] Incident Investigation with Uptycs and Osquery

[Video] Incident Investigation with Uptycs and Osquery

 

This video features Pat Haley, our Principal Sales Engineer, walking through the strengths and challenges of osquery, how osquery can be used for incident investigations, and how Uptycs can add value to an osquery deployment of any size.

Checking MDS/Zombieload mitigations on macOS with osquery

Checking MDS/Zombieload mitigations on macOS with osquery

As a part of a pretty crazy week (Microsoft/RDS, Apple/Mojave/High Sierra, Adobe Acrobat/ Flash Player) when it comes to security updates, some new speculative execution vulnerabilities were disclosed and fixed.

Page 2 of 3: