If I have to go through annual security awareness training, so do you.
@ESET may not enjoy this very much. It's threading time!
Well if someone markets to me under this name we know where it came from.
I... is this really necessary? I guess the 90 minute training's gotta be filled up with something.
"Meanwhile, Jackson's partner is cheating on him. Will he find out? Let's tune in..."
"You have a low-status job that's dull as watching paint dry, so you pretend you're saving the world with every decision you make."
Yup. Jackson works in infosec, all right.
"Here's how to detect whether an email is legitimate or not." I love how @eset has apparently not heard of "phishers who can spell properly" or "header inspection."
"The email isn't to the specific dedicated tagged address I gave Amazon years ago" is of course not on the list.
And of course "Amazon doesn't sign off with 'Best Regards' ever" is not on the list either.
"If you get a suspicious email, don't engage with it and put it out of your mind" means that I'll be ignoring a lot of emails. Like the inevitable @eset sales outreach.
"It's CRITICAL that you avoid opening a dodgy email attachment."
Uh... my rejoinder is "Why can me opening a file destroy the corporate network? This seems a lot like victim blaming to me. Maybe the Corporate IT folks need to upskill."
Apparently @eset should also "utlize" a spell checker.
This training seems to think that "spam filter" isn't software so much as it is an item in my job description.
This one's clearly spam but I bet @ESET doesn't know that. Why? Because Amazon hasn't told you what you ordered in their confirmation emails for *years* now.
Sorry, no. If "public wifi" is unsafe for you to use in 2022, your IT department has failed utterly. We're talking "contributed to the @ESET curriculum" level of failure here.
Bullet point 2 is sponsored by the entire RSA expo floor.
I would do all three of these because, again, it is 2022.
Hey, @internetofshit spotted in the security awareness training wilds!
"Check a company's privacy policy" is one hell of a lift, @ESET.
Yeah, no. If my employer cares about these things they can provide a separate router and uplink for business use. If not, they can shut the fuck up about what I do at home and mind their business.
Right after the "HTTPS is important" segment @ESET now goes to why a Web Content Filter is important. Uhh...
"One blocks or sets time limits on social media." If your employer does this, quit and get a job that treats you like an adult.
Now @ESET is telling me to be sure to install one to protect my kids.
This thread just shifted gears from "good natured" to "I actively wish harm upon @ESET."
Please tell me more about how to parent, you fucksticks.
"Switch off your Amazon Echo when doing work related things."
Again, "employment" does not equate to "you get to tell me how to behave in my own home."
Snitches get stitches, @ESET. This is once again Not My Job as an employee.
Sure is a lot of advice here that's only applicable to the physical office we don't have.
Yeah, I'm gonna challenge some beefy looking dude in a UPS uniform, @eset. It turns out I've reviewed my compensation and it nowhere near covers getting my shit rocked by an intruder.
"If someone reaches out to you first, it's suspicious."
Well yeah. The kind of corporate IT folks who subscribe to @ESET flat out don't do "proactive" in any sense. File a ticket, they'll get back to you eventually. Maybe.
Pretty sure the villain here is the mandated password rotation policy, @ESET. You'll find @NIST agrees with me.
The correct answer here is to track down your son's friend and break his little thumbs.
My god this artwork.
And nonsense complete and bahahahaha oh my god @ESET. "Here's how to fill out a badge for LinkedIn that doesn't actually validate a goddamned thing." Seems about right for your clownshoes level of technical understanding.
I'm at the AWS Summit in NYC, where I believe that nicknames are for friends--and Gennifer Artificial Intelligence is no friend of mine.
Good morning.
Thirsty much?
A game / challenge at the AWS Startups booth: how long can an AWS employee go without mentioning GenAI? Someone just made it all the way to one minute, ten seconds!
Okay. Let's do Networking Specialty. Practice question 1:
Correct answer is B.
"Wrong!" says the answer key, "it's B because network load balancers don't support client IP preservation."
Except that they do. They absolutely do. They have for the past year. I'm just a boy, standing in front of an AWS Cert team, asking them to do their damn jobs.
Today's cloud marketing story is called "The Tale of Hot Rebecca," and is a truthful recounting of dinner last night.
Strap in; it's a fun ride.
Back in my early 20s, I had a number of friends / acquaintances in my (primarily Jewish) social circle named "Rebecca." It was kind of a problem.
("Can't we spray for them?"
"…not since the 1940s.")
So every Rebecca got an adjective, much like the seven dwarves. One of them asked me once what her adjective was, and I responded in a fit of unadulterated honesty, "you're Hot Rebecca" because honestly? Damn.
Made it to the #GoogleCloudNext keynote seating finally. Let's see how this goes now that the world is starting to wake up to a "much of the AI hype is unwarranted" reality.
Boeing: "HOW ARE THEY DOING IT?!"
Airbus: "We bought a torque wrench?"
Boeing: "No, how are you being a featured customer testimonial at #GoogleCloudNext?"
Airbus: "Oh, that? We made a strategic decision to not be walking poster children for corporate negligence."
And now, some DevOps / SRE / Sysadmin / Ops / ENOUGH already tips I learned from early in my career--brought to us by our friends at Chex™ Mix. All of these are great ideas that you should implement immediately...
DNS is notoriously unreliable, so use configuration management to sync all of the servers' /etc/hosts files. Boom, no more single point of failure.
Future-proofing is an early optimization, so don't do it. Every network should be a /24 because that's how developers think. I mean come on, what are the odds you'll ever have more than 253 hosts in a network?
And the Amazon earnings are out for Q4. A miss on @awscloud revenue by $20 million because analysts didn't expect one of you to turn off a single Managed NAT Gateway.
Let's explore deeper into their press release.
For 2023, AWS sold $90.8 billion of services, most of which were oversized EC2 instances because you all refuse to believe Compute Optimizer when it tells you there are savings to be had if you're just a smidgen more reasonable.
Word frequency in the earnings release:
Customer: 87
Employee: 11
Generative: 16
Cloud: 24
Serverless: 3
DynamoDB: 2
Union: 0