Skip to content
View jberkers42's full-sized avatar
😃
😃

Block or report jberkers42

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
jberkers42/README.md

About Me

Hi there, my name is John - aka jberkers42

I'm a husband, father and Security Professional

My professional intersts include:

  • Security (which Security Professional is not interested in security?)
  • SIEM (Security Incident and Event Management)
  • DevOps/SecOps/DevSecOps (basically automating stuff)

Employment

I work at IPSec in Melbourne, Australia, having been there since the foundation of the company in late 2009, as a Senior Security Engineer, Architect and Consultant. I spend a lot of my time working with SIEM technologies, mostly LogRhythm, as well as a number of firewall and other security technologies.

My focus for the past couple of years has been to migrate more of our environment to the cloud, as well as increasing the level of automation for deployment and maintenance tasks.

Automation

There are two areas where I have focused on automation:

  • Infrastructure build and maintenance
  • Response from SIEM Alerts

For the former, most of the attention has been to implement automation and testing using Ansible to automate the implemtation and maintenance of our infrastructure. This has been achieved through the use of a combination of tools:

Infrastructure

GitLab repositories are used to hold the definition of the environment(s) as well as the instructions to build them. These are separated into functional layers:

  • Inventories
  • Roles
  • Playbooks

Ansible and AWX are used to execute the instructions against an appropriate inventory.

SIEM Response

One of the tents of a SOAR platform is to provide Automation and Response to an identified security incident. LogRhythm achieves this through the use of a SmartResponse™. SmartResponses are essentially a script wrapped with an XML file that tells LogRhyhtm how to execute it.

Most of my SmartResponse work has been in PowerShell.

Connect with me

jberkers42 BerkersJohn | Twitter jberkers | LinkedIn john.berkers | Instagram


Tools

Visual Studio Code SQL Git Ansible Azure AWS MarkDown LogRhythm GitLab PowerShell

Popular repositories Loading

  1. LR-Sophos-Central LR-Sophos-Central Public

    Sophos Central Parsing rules for LogRhythm

  2. Sophos-Central-SIEM-Integration Sophos-Central-SIEM-Integration Public

    Forked from sophos/Sophos-Central-SIEM-Integration

    Simple integration script for 3rd party systems such as SIEMs. Offers command line, file or syslog output in CEF, JSON or key-value pair formats.

    Python

  3. ansible-manage-lvm ansible-manage-lvm Public

    Forked from mrlesmithjr/ansible-manage-lvm

    Python

  4. jberkers42 jberkers42 Public

  5. LogRhythm.Tools LogRhythm.Tools Public

    Forked from LogRhythm-Tools/LogRhythm.Tools

    LogRhythm PowerShell Toolkit

    PowerShell

  6. powershell-module-template powershell-module-template Public

    Forked from theplatformer/powershell-module-template

    My PowerShell module project template for use with Plaster.

    PowerShell