Skip to main content

Yes, There Are Competent IT and Cyberprofessionals Out There, If You're Not Cheap.

The updated (and frankly, better written and edited) version will be on my Medium blog December 7th, 2020 with the title "The Myth of the Tech Talent Shortage and The Cost To Your Business."

My Medium profile is here.

This post is getting attention again: Hi. I like to think I've gotten less angry than when this was posted (Though I still think it's true, the times have changed with COVID-19, and I could have worded this more constructively). I'm pivoting to different areas of IT; Check the services and projects tag. 

 It's still BS that there aren't more part time positions in IT and tech. It's not like the talent isn't plentiful.

Atlanta, Georgia

Baltimore, Maryland

Newark, New Jersey

Savannah, Georgia

What do they have in common?

They have been the victim of serious cyberattacks on their infrastructure. Said attacks cost the affected city governments and companies more than 30$million dollars.

That's an amount Atlanta, at least, had been loath to use on helping people who want to live in their city, often ignoring those who have applied from out of state.

Maybe if they had dished up 2$million to cyber and IT people looking to relocate there, this could have been mitigated.  Or if people had basic knowledge about avoiding attacks, like opening emails from unknown senders.

Why are cities a growing target?

Because hackers know that cities often have stretched funds, and that the governments are populated with people who think IT and Cybersecurity are not necessary.

They know cities and the people who run them aren't growing quick enough to stand a chance against them, and that even the poorest cities can have a ransom fund big enough to fund a single person's life.

(I wonder if the people who attack cities tried to get legal Cyber jobs, but were turned away at every aspect?)

Baltimore, in particular, is doing pretty poorly; Using outdated practices by its own IT people. This is a tough job, yes, and it's easy to get lax when you're dealing with users who want things 'easy' and not secure.  Mistakes will happen, and nothing is infallible.

But this is about protecting a city's government and infrastructure. Standards should be taken, and there is only so much one person who is trying can do if they do not have the support they need.

While the methods of how they used backups aren't clearly stated, I can guess -

  • Backups once a year instead of once a month.
  • Said backups being kept on-site instead of somewhere else.
  • Probably stored on several physical mediums on the premises.

There were also 'important' people keeping files on their computers that were also compromised during an attack.

Cities and mayors - including Baltimore Mayor Bernard Young - aren't willing to pay the criminals. Which I think is perfectly fair. No need to set a precedent.
And yet, you will read time and time and time again on how there is a Cybersecurity talent shortage, or an IT talent shortage.

Which we know is a lie. So the question is;

When will cities be willing to pay Cybersecurity and IT professionals?

The salary of 3 competent cyber professionals is a lot less than the 30$m ransomware attackers are asking for.

"But no one has the experience!"

Systems can never be 100% secure, even if you remove them entirely from reaching the internet. However, I assure you, we have more experience than the people who want to pay a ransomware attack, or have weak passwords.

There is no shortage of IT and Cybersecurity talent; Just a shortage of people who realize they need it, and are willing to pay for it. You don't value your data, or the trust of the people whose data you have. That's a part of why you don't pay.

That ransomware attack on Baltimore? It'll cost at least 18.2$million dollars.

Maybe that's worth hiring a Cybersecurity professional or 3? Even with relocation involved?

And if you're going to be  cheap, well, audit your machines yourself, look for machines that may have open ports an attacker can sneak into, backup your data, and good luck when the next attack rolls around.

Because it will.


Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory