๐Ÿฅฉ๐ŸฅฉMr T-Bone tip!๐Ÿฅฉ๐Ÿฅฉ[New from Tech Community]
Stay ahead with the new GSA Operations Guide ๐Ÿš€ A handy playbook for running Global Secure Access with confidence, clarity, and fewer surprises ๐Ÿ” via MrTbone_se

#CyberSecurity #ITAdmins #MVPBuzz #Security #MicrosoftTechCommunity
๐Ÿ‘‰๐Ÿ‘‰ https://tip.tbone.se/G368Ju [AI generated, Human reviewed]

๐Ÿฅฉ๐ŸฅฉMr T-Bone tip!๐Ÿฅฉ๐Ÿฅฉ[New from Tech Community]
Fresh Intune goodness for May ๐Ÿš€ Handy updates, smarter management, and more to explore. Worth a peek from MrTbone_se ๐Ÿ‘€

#MicrosoftIntune #ITAdmins #MVPBuzz #Security #MicrosoftTechCommunity
๐Ÿ‘‰๐Ÿ‘‰ https://tip.tbone.se/g0fM1P [AI generated, Human reviewed]

#Linux #hivemind

TL;DR: How would you deploy a maintainable Linux build to 14 PCs?

I have a lab network of 14 PCs at $dayjob. I want them all to have the same Linux build/image, with the same apps - (probably) Plasma, VirtualBox, LibreOffice, Packet Tracer (so JRE as well) as the basics, plus various other tools.

If the users mess up the machine somehow, they need to be easily re-imaged. It would be nice if /home could optionally be preserved, but not essential.

I am currently the most Linux-savvy person in the team that will be looking after these PCs. I'm not there all the time, so this needs to be maintainable by techies who don't daily drive Arch.

I know #Ansible could be a good option, meaning I have some flexibility with which distro. (I am open to different distros for this.) #Nix or #NixOS could also work, but the learning curve for that could be pretty steep (for me - steeper for the rest of the team), plus its non-standard approach to Linux might be confusing for some.

I guess some solution using a PXE boot and then an auto-deployed script or definition file?

#ITAdmins #ITAdministration #AskFedi #SysAdmin

Oyster Backdoor Disguised as PuTTY and KeyPass Targets IT Admins via SEO Poisoning

Threat actors have been using trojanized versions of well-known IT tools like PuTTY and WinSCP to spread the Oyster backdoor.

GBHackers Security | #1 Globally Trusted Cyber Security News Platform

In the world of security information and event management (#SIEM) solutions, time to value can take longer than most #security teams want to admit.๐Ÿ’ฒโฐ This is why you want a well-structured initial setup for your SIEM. It will help you catch what matters most as well as set the stage for faster insights, reduced alert fatigue, and smoother handoffs between security, IT, and compliance. ๐Ÿ™Œ

Learn about 7 practical SIEM configurations that will help improve your time to value, so you can get the most security bang for your budget buck.๐Ÿ’ฅ

Dig into the details of these 7 best SIEM setup practices:
1๏ธโƒฃ Identifying basic use cases
2๏ธโƒฃ Selecting initial log sources
3๏ธโƒฃ Configuring data pipelines
4๏ธโƒฃ Routing data to chosen storage
5๏ธโƒฃ Setting user permissions
6๏ธโƒฃ Building detections and alerts
7๏ธโƒฃ Building dashboards and compliance reports

https://graylog.org/post/7-siem-configurations-to-improve-your-time-to-value/ #cybersecurity #infosec #ITadmins

Parsing JSON is the modern IT environment version of a colorful Trapper Keeper. ๐Ÿ—‚๏ธ ๐Ÿ“š ๐Ÿ“๐ŸŽ’ It's a widely-used, human-readable, and machine-readable data exchange format which structures data using text. ๐Ÿ”  It's a data-serialization standard that many programming languages support, which streamlines a programmer's ability to integrate and manipulate the data. ๐Ÿ‘

Let's take a closer look at JSON and learn:
โ“ How to make JSON readable
๐Ÿค” What it means to parse JSON
โ— Why JSON parsing is important
๐Ÿ’ป How to parse a JSON file
๐Ÿ‘ JSON logging best practices

https://graylog.org/post/what-to-know-parsing-json/ #devs #ITadmins

What To Know About Parsing JSON

Parsing JSON involves transforming structured information into a format that can be used within various programming languages.

Graylog