INFOSECC

I don't think I'm alone in my hatred for faxes, and I am 100% willing to be the face of the anti-faxxing movement. The facsimile is a relic of a bygone era. It should have died a graceful death, and been given a respectful "thanks for your service, and farewell" a few hours after Tim Berners-Lee revved up the World Wide Web in 1989. By now you've probably already seen the meme: But alas, here we are in the year 2021, still shoehorning faxes into the digital world. The reason they're still around, I suppose, is their simplicity. Feed the paper into a hungry machine, out it spits somewhere else, hopefully to its intended recipient.* Unfortunately for U.S.-based Healthcare IT professionals, the Centers for Medicare & Medicaid Services have been permissive of faxing for the transmission of protected health information. I, uh, have a bone to pick with this generally-accepted standard operating procedure, but I don't have the political power to persuade CMS

If the title scared you, don't let it. There's no physical effort to put forth in this hardening exercise, so you can safely continue to enjoy crunching down on Doritos dipped in peanut butter. (What? Just me on that one? Oof.) Anyway, to follow up on my Five Easy Security Wins in Windows post, I wanted to write about running LAPS. Because I'm not good at all with sport metaphors, let's just dive in. What is LAPS? LAPS stands for Local Administrator Password Solution, and it basically does what it says on the tin . As long as you use the same local administrator account name on your Windows endpoints, you'll be able to get LAPS set up in a matter of minutes. LAPS is a major and easy security win for Windows admins because it gives every endpoint a unique, randomized local administrator password. The passwords change as often as you tell them to, use whichever character sets you tell them to, and you can see what they are in the computer object's attributes in

I think I'm up to three times mentioning that I'm a minimalist now. Constantly assessing my need for all sorts of items has naturally spilled from my own house into my office... and Justin's office... and the server room... and the IT storage closets... and and and . I tackle clutter at home and at work, and I'd argue that it's especially necessary at work. Having a clean, clutter-free workspace makes life at work easier... and it allows for old materials to become new through e-waste recycling. Chucking all the old hardware (old as in it hasn't been in service since dinosaurs roamed the earth) into a giant pallet box is the easy part. Disposing of electronic waste like you would do with regular trash is generally ill-advised, if it isn't outright illegal where you live. What do you do next? Well, if you're a responsible denizen of the planet, you'll want to recycle as much of the old equipment as possible. If you've got a full pallet box of e-w

Yes, you read the title correctly. Using *nix operating systems has indeed made me a better Windows sysadmin. It shouldn't be all too surprising, especially since the proclamation years ago that Microsoft <3s Linux , and I don't think systems administration should be played as an either/or game between Windows and Linux environments. There is so much that we Windows sysadmins can gain by taking deep dives into *nix operating systems as part of a healthy production environment. My experience with Ubuntu Server has made the biggest impact to me as a Windows sysadmin. In Windows environments, I'd grown accustomed to having the desktop experience (GUI) as the primary mode of getting everything done. Need to run an application? Click around. Need to set up a service to start automatically? Click around. Granted, with Windows Server OSes there is a headless (Core) option, but let's be honest and admit that probably none of us use it because it feels weird. In Ubuntu Server

If you walk into my family's home, you may find it cluttered with toys and books and other miscellaneous messes created by our four children, but what you will not find are scattered bills laying about. For that, and other paper-centric processes, I have a system which has evolved over the years, to the point I'm actually pretty happy with it. The small apartment we occupied in the mid 2000s was right-sized for our dog, cat, my wife and me. To ensure we didn't accumulate paper clutter, I began the process of scanning any bill or receipt that ended up on the counter, and tossing it right away. It was at this point I became enamored with the YYYY-MM-DD naming convention for dates, as it made things easily sort-able in a directory. Each file I dumped on my PC was backed up to DropBox . This system was okay, but not particularly useful when it came time to try to find something. In 2010 or so, I started dumping everything into  Evernote . Receipt? Evernote. Bill? Evernote. Bank

Every communication medium we've ever invented as humans has, at some point, been pressed into service as a malicious tool. A lot of us do what we can to use such tools for good, or at least for benign purposes. The worse-but-not-quite-worst of us humans love to hack, scam, and swindle others to get what they want. With Microsoft Windows having such a huge marketshare versus 9,001 flavors of Linux and Apple's Mac OS, MS's operating systems and programs are huge targets for malicious actors. As a Windows sysadmin first and foremost, I feel that pain and do what I can to keep my users safe. (Side note: I also love to waste scammers' time--if they're talking to or emailing me, they're not using that time to take advantage of someone more trusting and/or gullible.) And despite being primarily a Windows sysadmin, I'm also a lover of open-source-everything, ESPECIALLY knowledge. Below, I'm going to share five easy(ish) things you can implement to beef up your

Justin and I are an amazing team. Then again, we kind of have to be as a two-person team. Before Justin decided I was worthy of being his insubordinate subordinate, I had always worked on fairly large teams--12 or so people in small companies. I have to say that not a day has gone by since I left my last job that I've missed having a larger team. With it being just the two of us, we get a much higher volume of work done faster and better than I've ever seen happen on larger teams. The benefits: We don't have to: run our ideas by a room full of people to reach a consensus wait for internal bureaucracy to approve every last little project or purchase waste time having meetings waste even more time having meetings about other meetings spend a chunk of the day responding to emails from other team members work around each other's in/out time to work on a group project send emails back and forth to keep everyone in IT in the loop stay locked in to vendor relationships set up

When Monica and I talked about doing a blog, we knew there would be no shortage of ideas for posts. But before we could start churning out amazing content, we had to decide on a platform. I had an idea. I'm by no means a Django expert but it's a great tool, and I have a tendency to reach for it when I need to do a web thing. Django, a postgres db, maybe sprinkle in a rest API... perfection. The best tool; perhaps not the right tool Monica did not share this wholesome, perfect vision. She reasoned that we are already, and will continue to be, plenty busy, and do we really need to spin up our own thing when there are perfectly viable drop-in options available on the web without us needing to worry about hosting a thing and dealing with the security risks, backup strategies, etc.? Wordpress or Blogger would do just fine. Damn. Well, she'll come around. I pursued Wagtail and was in the process of going through a tutorial and, I was loving the freedom and openness of the platf

Single-purpose servers are my hot mashed fruit. As a minimalist, I don't like clutter, and that extends into computing environments. Although it might sound kind of crazy to spin up a new server for every little thing, I promise it will make sense by the end of this post. From a management perspective, having single-purpose servers makes it so much easier to know which services are running where. Basically think of this like delegating tasks among team members to get projects done quickly and efficiently. I'm a documentation junkie, and it drives me bonkers when I see a server that's just got too much on its plate--we're not running a steakhouse here--keeping things simple keeps them running smoother. As a result of not cluttering servers with every possible service to run, my documentation stays clean and readable. Single-purpose setup also means that I can set the less mission-critical services and devices to update and restart in the middle of the day and have little

 If the title of this post got any more exciting, we'd have to sell tickets. We both use Manjaro Linux, but we each use it much differently than the other. Each of our approaches is detailed below. Pick your fighter and may both teams win. In the first corner of the ring (corner of a round thing, ehck)... Monica's "Woman"jaro. Monica's Minimal Manjaro Linux (Mmm, Linux) My approach to Manjaro Linux is to have a Windows environment without running Windows. I start with the minimal iso of Manjaro and build it up to run only the software I want, and none that I don't. Side note: I also run a blog on minimalism, so go figure I don't like digital clutter. Ease of gaming and working both inform my Linux setup style. I've been immersed in PC gaming since 1993 and thought for about 20 years after the fact that I'd be locked into Windows forever to keep things easy. My first foray into an attempt at gaming on Linux came in 2006 with Ubuntu. I loved the OS b

Hi! Welcome to this thing. I'm Justin, this is Monica [gestures in a direction]. We're a friggin' awesome two-person team managing an IT department at a rural hospital in Nowheresville, MN. In this space, we hope to chronicle our challenges, lessons, wins, and losses. Maybe not the losses. IDK. I am putting minimal effort into this intro piece because we plan to bury it with interesting content in short order.  And sneaking in (this is Monica, btw, I use Arch), we're going to aim to not make our content dry and boring. It'll be... moist and exciting? Or at least damp and riveting. Check the About Us page to learn more about our goals with the blog, and about us as techies. Thanks for visiting & keep your eyes peeled for actual content coming soon!