<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reverse-Shell on clo.ng</title>
    <link>https://clo.ng/categories/reverse-shell/</link>
    <description>Recent content in Reverse-Shell on clo.ng</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 21 Jan 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://clo.ng/categories/reverse-shell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Osquery to Detect Reverse Shells on MacOS</title>
      <link>https://clo.ng/blog/osquery_reverse_shell/</link>
      <pubDate>Sun, 21 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://clo.ng/blog/osquery_reverse_shell/</guid>
      <description>&lt;h2 id=&#34;reverse-shell-detection&#34;&gt;Reverse Shell Detection&lt;/h2&gt;&#xA;&lt;p&gt;One challenge when it comes to building defenses for MacOS are the numerous scripting languages that come pre-installed with the operating system. While it may be convenient for developers, it provides attackers with a variety of methods for establishing persistence and bootstrapping connections to command and control servers.&lt;/p&gt;&#xA;&lt;p&gt;Once attackers gain a foothold on systems, they frequently like to gain shell access by launching reverse shells. The benefits of this are well documented &lt;a href=&#34;https://andreafortuna.org/cybersecurity/some-thoughts-about-reverse-shells/&#34;&gt;here&lt;/a&gt;. As you might expect, there are numerous ways to initiate these connections using native utilities such as:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
