Call for Papers

BSidesLV is committed to keeping our conference vendor-pitch free. Any abstracts that reflect a sales approach or talk of the product and not the tech will be rejected out of hand. Speakers sneaking a sales or product pitch in under the guise of a tech talk will be pulled from stage and publicly shamed and humiliated on Social Media. All talks are vetted through our CFP committee, and any talks submitted on behalf of someone else (i.e.: not submitted by one of the primary authors) will not be considered.  We do not typically compensate speakers for travel or accommodations expenses or pay appearance fees.

Please refer to the Sample Submission below, for proper formatting!

We are excited to hear what you have to share, and look forward to seeing all of you in August!

Author Guidelines

Sample Submission

Note to the reader: This is not intended to be a perfect, canonical instance of a submission, but it does illustrate what types of information to include, the LOWEST level of detail to use, and the overall flow of a good submission.

The more concrete data and context you can provide on your assertions and their impact, the more accurately we’ll be able to assess how interesting the research/concepts you are sharing will be to our participants, and how your talk will fit into the overall balance of the event.

Did you implement your recommendations anywhere?  What was the result?  How many more root shells did you get, how much faster or with how much less tester time?  How prevalent are the unresolved attack vectors you’re trying to get industry to address, and what are the financial or other costs of ignoring them?

What reduction did you achieve in analyst turnover?  How much did you improve mean time to detection for breaches in your org?  How much more of your organization’s code base is getting audited intelligently because you’ve automated away XSRF detection and prevention?

What failures/problems did you have before you learned your lessons and how successfully are you avoiding them now?  Tell us how amazing your amazing is, because we love your amazing and we want everyone else to love it too.

1. Title of Presentation

Template Management Using Osiris

2. Presenter(s) Name(s)

Bruce Potter

3. Abstract

Osiris is an open source integrity monitoring software system written by the Shmoo Group many years ago. It is used in many organizations as a scalable means to monitor for changes created by change management violations and penetration by external actors. One of the challenges with Osiris (and any integrity monitoring tool) is minimizing the amount of noise created by inconsequential changes. Osiris addresses this problem through the use of templates that limit the scope of monitoring based on the host OS and user customizations. Unfortunately as OS’s evolve, the set of files that SHOULD be monitored can often change and osiris templates don’t account for these changes.

We have developed a lightweight tool to monitor running systems to instrument changes over time and ultimately recommend changes to the currently deployed templates. Rather than performing full blown scans and checksumming to look for changes, this tool will only examine MAC times thereby dramatically reducing a “normal” instrumentation scan. Administrators are able to look at the statistical data under the tool and determine what changes to accept to the running template. We have also developed a public database of templates based on results from the tool so that organizations can provide updated templates back to the community.

4. Detailed Outline

  • Who we are (3 mins)

    • We’re The Shmoo Group. We developed osiris originally and for many years it was maintained by member Brian Wotring. We have many years experience in integrity monitoring research, engineering including leveraging hardware modules to provide better assurance of integrity measurements.

  • Quick Osiris Background (5 mins)

    • Osiris is a multi platform integrity monitoring tool that has been widely deployed. However, many in the audience may be unfamiliar with how it works. We’ll provide an architectural overview of Osiris and discuss a few use cases

  • The Problem with Template “Drift” (15 mins)

    • Over the last year, we’ve examined several operating systems and examined how and when core, critical files were moved to new locations/names/etc. These changes were usually occurred during the application of patches rather than administrative activities. We will present data on how large the problem is and how the movement (or “drift”) of these files caused some of them to fall out of bounds for the existing Osiris templates

  • A lightweight solution (15 mins)

    • The whole purpose of Osiris templates is prevent scanning all files on the filesystem. A scanner that attempts to identify drift through checksumming would be counterproductive to the performance goals of Osiris. Our solution was to examine the MAC times of all files on the filesystem as a low priority thread. We then examine the MAC times and look for files that fall in to the following 3 buckets

    • M/C time did not change and file is in Osiris template (good)

    • M/C time changed a small number of times (1-2), nearby files did the same. Files not in Osiris template (candidates for inclusion)

    • M/C times changed constantly. Files outside Osiris template (probably user specific files that aren’t system security relevant. Not a good candidate for inclusion)

  • Demo (10 mins)

    • We’ll show the interface we created for template management and demonstrate the process an administrator goes through to update system templates. We’ll also demonstrate our database and service that can help jumpstart an administrator’s modifications.

  • Questions (2 minutes)

5. List of other conferences

We presented our data on system file drift at BSides Antarctica in July. However that research has been updated and the tools and database are completely new.

6. Why is this a good fit for BSides LV

We feel that integrity management is an important capability for any modern enterprise, especially with the ease of which adversaries can modify attacks and malware to avoid detection by AV and IPS. We feel that our template update system provides a key component that is otherwise missing in integrity management systems.

7. Previous experience

We have presented at BSidesLV  before. We have also delivered presentations at DefCon, Blackhat, The Gathering of The Shmoo, and InfoSec Anonymous.

8.  You can see video of our best previous presentation here

9. List of facilities requested

We need to be able to project 2 different systems at one time for our demonstration. Please let us know if that’s a problem as we’ll retool our demo to accommodate one screen.

Submissions for this conference were closed on 2018-05-24.

© 2018 Security BSides Las Vegas, Inc.