0103, 2024

Driving Change: Advocating for Tech and Privacy Regulations with Congress for a Safe and Free Online World

Ryan Glynn/ March 1, 2024/ Security and Technology/ 0 comments

These issues affect everyone, regardless of political affiliation, and we need to make our voices heard. The internet has become an essential part of our lives, enabling us to communicate, work, learn, shop, and entertain ourselves. However, the internet also poses significant challenges and risks, such as cyberattacks, identity theft, data breaches, and censorship. That is why we need regulations

0103, 2024

Chaotic Comforts: IOT Device Reviews for Privacy and Security

Ryan Glynn/ March 1, 2024/ Security and Technology/ 0 comments

How I will test and review the latest gadgets and devices for your home Hey everyone! It’s 2024 and I am officially trying to get back into blogging! If you haven’t read it yet, I just posted an in-depth analysis I conducted last year on Alexa, aiming to determine if it listens and reports back to Amazon when the wake

0103, 2024

Alexa Espionage: Uncovering The Truth Through A Quick Network Analysis

Ryan Glynn/ March 1, 2024/ Security and Technology/ 0 comments

TL;DR Intro: Something always appears to be creeping on conversations. It can sometimes be felt when you have a conversation, and without ever googling the topic, you suddenly see ads related to the product. Perhaps the Baader-Meinhof phenomenon is truly what’s happening, but there’s always a chance it isn’t – given how sketchy a lot of aspects of social media

2703, 2019

How to Blue Team: Detecting Weaponized Office Documents on Apple Macs (OS X)

Ryan Glynn/ March 27, 2019/ Security and Technology/ 0 comments

Introduction to How to Blue Team: There’s a lot of documents on how to use pen testing tools, how to crack, hack and break into things. Not a lot is written on how to detect these things, especially at the “Enterprise” level where a lot of the blog posts seem to give use cases that do not scale well. So,

2603, 2019

How to Blue Team: Detecting WinRar Ace32 Exploits (CVE-2018-20250) Using Sysmon

Ryan Glynn/ March 26, 2019/ Security and Technology/ 0 comments

1509, 2018

How to Blue Team: Detecting USBs Spawning Scripts (Malware Infected USBs) on Windows machines

Ryan Glynn/ September 15, 2018/ Security and Technology/ 0 comments

2608, 2017

The Truth About The “Splunk versus Elk” Debate

Ryan Glynn/ August 26, 2017/ Security and Technology/ 0 comments

The Truth About the Splunk versus ELK Arguments I feel the need to write this because of how many dishonest articles there are about the Splunk vs ELK debate. It seems like either the writers used both applications for a single day and knew the bare basics or that they have extraordinarily simplistic use cases to test. So, naturally, I

2408, 2017

Creating a Splunk bashrc Profile for Easy CLI

Ryan Glynn/ August 24, 2017/ Security and Technology/ 0 comments

One of the things that makes doing Splunk operations and infrastructure work so much easier and faster is having a bashrc profile (assuming you’re running Splunk for Unix) that aliases a lot of the common commands. This is a quick step by step on how to create a bashrc profile for Splunk. Create a bashrc profile for the default ssh

2408, 2017

Splunk Tips and Tricks Part 1: Search and Reporting Tips

Ryan Glynn/ August 24, 2017/ Security and Technology/ 0 comments

Over the years I have collected some basic (and advanced) tips and tricks for utilizing Splunk – both from an operational standpoint of server maintenance as well as from the standpoint of alert, report and dashboard creation. Below are some of the most basic search tips that I have, additional posts are to follow for more advanced tips and tricks.

2308, 2017

Python3 Script to Retrieve Entries using LDAP3

Ryan Glynn/ August 23, 2017/ Security and Technology/ 0 comments

Below is a script I wrote to pull large data sets of Active Directory data using Python 3 and ldap3. I didn’t see any blogs that fulfilled my particular use case so I figured I would post a working version that I have. I have truncated all sensitive information out with <TRUNC> so be sure to replace that with the respective