You make it sound as if it's a thing of the past when it is still a common problem.

And yet injection is still #3 in the OWASP Top 10

This article is AI generated SEO spam.

I set up Netbox recently at work to try and improve the abysmal documentation situation. I use an Ansible playbook to provision and set up the server, then copy a docker compose file and start the containers. So far I'm loving Netbox, I just wish my predecessors had documented things from the start.

Namecheap + the dynamic DNS client in pfSense. No issues sinve I set it up years ago.

Before that it was a cron job that updated through the google domains api.

Da Archive maybe? Most of my stuff has come from there.

Stay suspicious. As a security guy, i'd way rather respond to 1,000 false positive reports than have an employee that doesn't think about it and just clicks.

It is a great step but it's rare to have enough buy in from upper managent to enforce any real consequences for repeat offenders. I've seen good initial results from this kind of phishing testing, but the repeat offenders never seem to change their habits and your click rate quickly plateaus.

A little late, but here is what I usually do when a ticket like that comes in:

1. Check monitoring. It's quick and easy to check so I'll look before even asking any clarifying questions. If there is a real network problem at a site, 95% of the time its going to show up on our monitoring dashboard. Everything from ISP outages to device failures show up here.
2. Ask for more details about what they are trying to do. What is the goal? What are you doing? What is happening? What should be happening? When was the last time it worked?
3. Based on those details, I can usually put together a good guess as to what might be going on, so i'll test that theory out and see if i'm right.

Oh thanks, saved. Will break this image out next time it happens, though I usually end up dying from getting into desperate situations looking for antifungals before it gets to this point.

Thanks! This is actually exactly what I have been basing my efforts on so far, it's just sobering to look at how far away we are from completing implementation group 1.

I just started my first official cybersecurity position at a medium size company in an industry that is currently being heavily targeted with ransomware.

I'm starting pretty much from scratch as they have not had a dedicated security role in over a year and my predecessor didn't make much progress. So far i've been focused on inventory lists, policies, and procedures for hardware, software, and data. I think we're doing okay with minimizing stuff thats internet facing and patching is in a good place (well, at least with the devices and os's that are still supported).

Any suggestions on where to go from there or what to prioritize?

I'm studying for CCSP right now. It's fairly general and tries to be vendor neutral but Architecture is one of the knowledge domains on the exam. Might be worth it if you meet the work requirements or experience waiver requirements.

A lot of people also seem to conflate it with the CISSP when it comes up in conversation I've noticed.

Curation is my answer. Return to the old ways of curating your own lists of resources and sharing them with other people. Web rings, blog rolls, link sharing, RSS

As someone in the thick of it, it has been a nervewracking quarter for mortgage company IT and Infosec teams. There have been several very high profile breaches the last few months.

Oh MediaTracker looks nice, thanks!

I now want a roleplaying game set in village like this.

.1Q because Q has a tag on it

Oh I highly recommend it. As a kid I read a lot of his work and my favorites were the Cask of Amontillado and The Tell-tale Heart. I still love those ones but I feel like I can appreciate the poetry and other stories now.

Another series I've gotten a lot of mileage out of revisiting was Calvin and Hobbes funny enough.

Oh nice, have you read any of his other books? I keep meaning to get around to reading Bullshit Jobs.