<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jas on Medium]]></title>
        <description><![CDATA[Stories by Jas on Medium]]></description>
        <link>https://medium.com/@jason.gerfen?source=rss-c336800354a5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*eVHXsSrVaP2DgX9y</url>
            <title>Stories by Jas on Medium</title>
            <link>https://medium.com/@jason.gerfen?source=rss-c336800354a5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 02:10:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jason.gerfen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[stigadm; in its infancy…]]></title>
            <link>https://medium.com/from-the-ether/https-medium-com-from-the-ether-stigadm-6c8aedf0a739?source=rss-c336800354a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c8aedf0a739</guid>
            <category><![CDATA[stigadm]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[stig]]></category>
            <category><![CDATA[oval]]></category>
            <category><![CDATA[unix]]></category>
            <dc:creator><![CDATA[Jas]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 21:46:38 GMT</pubDate>
            <atom:updated>2018-11-19T11:39:04.314Z</atom:updated>
            <content:encoded><![CDATA[<h3>stigadm; infancy stages…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cMKB5G5DZc5_uhBMzvKZYA.png" /><figcaption>stigadm; cryptographic communication examination per Solaris 11 STIG ID’s V-48159, V-48161, V-48163, V-48167, V-48171, V-48175 &amp; V-48179</figcaption></figure><p>Conformance to information assurance requirements is essential to minimizing attack vectors. Eliminating or mitigating known <a href="http://cve.mitre.org/">CVE’s</a>, using <a href="https://csrc.nist.gov/projects/security-content-automation-protocol">SCAP</a> as defined in <a href="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-70r4.pdf">NIST’s SP 800–70</a> to address <a href="https://www.pcisecuritystandards.org/security_standards/documents.php?association=PCI-DSS">PCI-DSS</a>, <a href="http://usgcb.nist.gov/">USGCB</a> &amp; <a href="http://iase.disa.mil/stigs/Pages/index.aspx">STIG</a> recommendations helps maintain a high security posture in today’s infrastructure.</p><p>For most, implementing STIG compliance is done using a tool such as <a href="https://www.open-scap.org/">OpenSCAP</a>, <a href="https://www.ansible.com/security-stig">ansible</a> or manual configuration. However performed, this should be an automated, repeatable and easily configured process that matches the target environment.</p><p>“Use OpenSCAP!”</p><p>Yes, absolutely, it checks the box. By parsing the <a href="https://oval.mitre.org/">OVAL</a> &amp; <a href="https://csrc.nist.gov/projects/security-content-automation-protocol/specifications/xccdf/">XCCDF</a> to validate or provide remediation for the provided STIG rule. You cannot ignore the simplicity.</p><p>However simple to use, some of the rules defined are difficult, time consuming and prone to human error when validating or implementing.</p><p>As an example, take the following CAT-II rules:<br><em>AIX:</em> <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-906">V-906</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-907">V-907</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-910">V-910</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-4089">V-4089</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-4090">V-4090</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-4091">V-4091</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-22354">V-22354</a>, <a href="https://www.stigviewer.com/stig/aix_6.1/2018-04-10/finding/V-22355">V-22355</a><br><em>HP-UX:</em> <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-906">V-906</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-907">V-907</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-910">V-910</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-4089">V-4089</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-4090">V-4090</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-4091">V-4091</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-22354">V-22354</a>, <a href="https://www.stigviewer.com/stig/hp-ux_11.31/2018-03-01/finding/V-22355">V-22355</a><br><em>OEL:</em> <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-906">V-906</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-907">V-907</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-910">V-910</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-4089">V-4089</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-4090">V-4090</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-4091">V-4091</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-22354">V-22354</a>, <a href="https://www.stigviewer.com/stig/oracle_linux_5/2018-03-01/finding/V-22355">V-22355</a><br><em>RHL:</em> <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-906">V-906</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-907">V-907</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-910">V-910</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-4089">V-4089</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-4090">V-4090</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-4091">V-4091</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-22354">V-22354</a>, <a href="https://www.stigviewer.com/stig/red_hat_enterprise_linux_5/2017-03-01/finding/V-22355">V-22355</a><br><em>Solaris:</em> <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-906">V-906</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-907">V-907</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-910">V-910</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-4089">V-4089</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-4090">V-4090</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-4091">V-4091</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-22354">V-22354</a>, <a href="https://www.stigviewer.com/stig/solaris_10_sparc/2018-04-10/finding/V-22355">V-22355</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59827">V-59827</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59831">V-59831</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59833">V-59833</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59835">V-59835</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59837">V-59837</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59839">V-59839</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59841">V-59841</a>, <a href="https://www.stigviewer.com/stig/solaris_11_sparc/2018-04-10/finding/V-59843">V-59843</a></p><p>All of which indicate possibilities for <a href="https://attack.mitre.org/wiki/Privilege_Escalation">local privilege escalation</a> that do not require a vulnerable process. They also make a great example where more is required than the fix text that is defined in the OVAL.</p><p>Regarding the rules mentioned; it may or may not be clear that the startup service configuration files may contain references to other files which would also require the same validation that is not easily validated with the OVAL fix text.</p><p>Some possible conditions that make this a difficult example for automation is absolute vs. relative paths &amp; handling the various inclusion methods. A problem that <em>“manual inspection”</em> as a solution will undoubtedly overlook.</p><p>Here is an <a href="https://gist.github.com/jas-/89fa126e02ae0c51b9fe48f472827232">automated solution</a> to cover the above STIG ID’s in depth. The script performs a deep dive on the available service file(s) for <a href="https://www.tldp.org/HOWTO/HighQuality-Apps-HOWTO/boot.html">init.d</a>, <a href="https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-services-xinetd.html">xinit.d</a>, <a href="https://www.linux.com/learn/understanding-and-using-systemd">systemd</a> &amp; <a href="https://www.oracle.com/technetwork/articles/servers-storage-admin/intro-smf-basics-s11-1729181.html">SMF</a>. Once it acquires a list of available service manifests it plucks out potential file(s) and examines the user, group &amp; permissions of the referenced file as well as the configured LD_LIBRARY, PATH and other environment definitions for malformed or suspicious entries.</p><p>Perhaps now is a good time to introduce the <a href="https://github.com/stigadm/stigadm">stigadm</a> project. While the example provided is a prototype of the modules included with the project, it should provide a clear indication of functionality with regards to the intent of the project.</p><p>If you wish to know about the reasons another security tool is under development where there seems to be <a href="https://oval.mitre.org/adoption/productlist.html">so many</a> tools already; you can use <a href="https://opensource.org/licenses">open source licensing</a>, flexible configuration for the target environment, curated for accuracy and provides an API for others to contribute.</p><p>Features include support for classification targeting, <a href="https://gist.github.com/jas-/431d107d3d744ba7ba41bf3b8d5cbdcf">XML/JSON reporting structures</a>, modes for validation (default), remediation and restoration, a <a href="https://github.com/stigadm/stigadm/tree/master/build">build system</a> to create STIG modules based on XCCDF parsing for AIX, HPUX, OEL, RHEL, Solaris &amp; Ubuntu and the whole thing is in bash.</p><p>This article is to serve as a call to others implementing STIG hardening to possibly <a href="https://github.com/stigadm/stigadm/blob/master/CONTRIBUTING.md">contribute</a> your expertise. As you can discern from the code coverage report that contributions would help push this project along.</p><p>Far from complete, but should be a good path to a robust modular solution.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c8aedf0a739" width="1" height="1" alt=""><hr><p><a href="https://medium.com/from-the-ether/https-medium-com-from-the-ether-stigadm-6c8aedf0a739">stigadm; in its infancy…</a> was originally published in <a href="https://medium.com/from-the-ether">from the ether</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forensics; Linux anti-virus the hard way]]></title>
            <link>https://medium.com/from-the-ether/forensics-linux-anti-virus-the-hard-way-640a8e3148d5?source=rss-c336800354a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/640a8e3148d5</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[antivirus]]></category>
            <category><![CDATA[yara-rules]]></category>
            <category><![CDATA[recall]]></category>
            <dc:creator><![CDATA[Jas]]></dc:creator>
            <pubDate>Sat, 13 Oct 2018 04:36:02 GMT</pubDate>
            <atom:updated>2018-10-13T04:36:02.077Z</atom:updated>
            <content:encoded><![CDATA[<p>As most of us know linux and unix do not typically use anti-virus. While software does exist to assist with with <a href="https://www.webopedia.com/TERM/V/virus_signature.html">signature</a> or <a href="http://www.toptenreviews.com/software/articles/what-is-heuristic-antivirus-detection/">heuristic</a> based analysis it is not as common.</p><p>While anti-virus software does assist remediation of computer virii, most users are unaware of their effectiveness. It has been said that any common exploit; <a href="https://en.wikipedia.org/wiki/Computer_virus">virii</a>, <a href="https://searchsecurity.techtarget.com/definition/worm">worms</a>, <a href="https://www.veracode.com/security/rootkit">rootkits</a>, etc. go unnoticed on average three to six months or more before one can be <a href="https://www.symantec.com/security-center/writeup/2010-071400-3123-99">analyzed</a> and a signature created.</p><p>Three to six months may like a long time, however think about the complexity of the modern day computing environment. Exploits in any form can hide in <a href="https://www.engineersgarage.com/definitions/what-is-memory-resident-virus">memory</a> segments, attach <a href="https://www.techopedia.com/definition/4055/polymorphic-virus">polymorphic-ally</a> to running processes, inject themselves into hard disk <a href="https://www.kaspersky.com/blog/equation-hdd-malware/7623/">firmware</a> etc. The current state of detection rests solely in the actions of a knowledgeable systems administrators, the attentive end user or use of automated traps such as <a href="https://searchsecurity.techtarget.com/definition/honeynet">honeynets</a> &amp; <a href="https://searchsecurity.techtarget.com/definition/honey-pot">honeypots</a>.</p><p><a href="https://www.makeuseof.com/tag/free-linux-antivirus-programs/">Anti-virus</a> solutions are available and can aid in both hardening your system as well as keeping it free of infection. Occasionally however, the examination of a system for root cause analysis might require additional tools to help you separate the wheat from the chafe.</p><p>Previously the article titled ‘<a href="https://www.linkedin.com/pulse/forensics-volatile-memory-acquisition-jason-gerfen/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BhhO23DICSniwhDXvV%2BhocA%3D%3D">Forensics; volatile memory acquisition</a>’ focused on a toolkit available from Google called <a href="http://www.rekall-forensic.com/">Rekall</a>. This handy tool can assist forensic investigations by seeking out known signatures within volatile memory using a well known tool in the virus research arena called <a href="https://virustotal.github.io/yara/">YARA</a>. This can be extremely handy to narrow down known compromises, however buyer beware it can yield quite a few false positives.</p><p>The <a href="https://gist.github.com/jas-/a450a5b46356a6c701e16b0144b9bd8b#file-rekall-inspect-with-yara-sh">rekall-inspect-with-yara.sh</a> shell script can be used to compile the necessary Linux profile, examine all available linux plugins as well as sift through memory for patterns matching the many pre-built <a href="https://github.com/Yara-Rules/rules/">YARA rules</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=640a8e3148d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/from-the-ether/forensics-linux-anti-virus-the-hard-way-640a8e3148d5">Forensics; Linux anti-virus the hard way</a> was originally published in <a href="https://medium.com/from-the-ether">from the ether</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Forensics; volatile memory acquisition]]></title>
            <link>https://medium.com/from-the-ether/forensics-volatile-memory-acquisition-a367565d7ed5?source=rss-c336800354a5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a367565d7ed5</guid>
            <category><![CDATA[recall]]></category>
            <category><![CDATA[memory-acquisition]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[anti-forensics]]></category>
            <dc:creator><![CDATA[Jas]]></dc:creator>
            <pubDate>Sat, 06 Oct 2018 03:27:52 GMT</pubDate>
            <atom:updated>2018-10-06T03:27:52.137Z</atom:updated>
            <content:encoded><![CDATA[<p>While feeling confident in limiting the amount of surface area an attacker might use to get onto a system, one thing that holds additional weight is; how to verify the suspicion of compromise? Some exploits are quite obvious. However, in the event of what seems like a normally running system how can we be 99.999% certain it is not compromised?</p><p>Obviously a misbehaving application, a bit of network activity or even a logged event might trigger such an investigation of your system. How, as an administrator, to know what to look for and determine if a system is indeed compromised before it spreads when there isn’t any clear indication of compromise?</p><p>With recent trends in malware, viri, rootkit, persistent boot-kit infections, polymorphic memory resident and process attachment functionality might push computer security into this traditionally niche realm of computer forensics.</p><p>Approaching new system builds with security in mind involves things like building it offline, adding layers of security such as disabling unwanted/needed services, restricting application &amp; system user accounts, tuning network and OS kernel parameters, ensuring the boot ROM code, device firmware and OS are using the latest patches and security configurations, implementing IDS &amp; IPS, network ACL’s and making use of file system integrity tools.</p><p>To better aid anyone’s role as a systems administrator, exploring best practices for computer forensics is the next logical step. How better to ensure the protections implemented are working then to examine running memory and interpreting those results?</p><p><a href="http://www.rekall-forensic.com/">Google’s Rekall</a> is a forensic framework based on <a href="http://volatilityfoundation.org/">Volatility Foundation</a>. An anti-forensic memory acquisition feature described in detail <a href="https://www.dfrws.org/sites/default/files/session-files/paper-anti-forensic_resilient_memory_acquisition.pdf">here</a> meant to target those rootkits that are advanced enough to prevent forensic analysis is by far its largest selling point.</p><p>Two modes of operation are available; dump memory to file for inspection offline (<em>by far the better option</em>) or to inspect memory real time. While a hardware based acquisition is by far the <em>best</em> option; however the cost of a dedicated device is still very costly, making it unreachable for the majority of us.</p><p>Like any software based methods of memory acquisition Rekall &amp; Volatility frameworks are indeed susceptible to <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.sciencedirect.com%2Fscience%2Farticle%2Fpii%2FS1742287613000583&amp;sa=D&amp;sntz=1&amp;usg=AFQjCNETYYIIkPc1cckO1Pt1jOYWm0a8_Q">Anti-Forensics techniques</a> leaving the investigator with little recourse than to use live memory investigative techniques. This will likely create problems in regards to time and results as open processes, files on disk &amp; open network connections of the running rootkit and/or modern EFI bootkit will likely result in an incomplete snapshot of the compromised system.</p><p>To help you I have put together a simple method of iterating a set of <a href="http://rekall.readthedocs.io/en/latest/plugins.html#linux">plugins</a> available. Please visit the <a href="https://gist.github.com/jas-/a450a5b46356a6c701e16b0144b9bd8b#file-rekall-inspect-sh">rekall-inspect.sh</a> gist I have setup for details of the simple (very simple) automated live memory acquisition script. It helps facilitate a quick profile build based on the running kernel and outputs all plugin output to a timestamped folder to preserve the order of volatility.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a367565d7ed5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/from-the-ether/forensics-volatile-memory-acquisition-a367565d7ed5">Forensics; volatile memory acquisition</a> was originally published in <a href="https://medium.com/from-the-ether">from the ether</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>