Technology

58996 readers

4144 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

Keep Tier-One Applications Out of Virtual Environments (www.darkreading.com)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]

35 comments fedilink hide all child comments

After reading this article, I had a few dissenting thoughts, maybe someone will provide their perspective?

The article suggests not running critical workloads virtually based on a failure scenario of the hosting environment (such as ransomware on hypervisor).

That does allow using the 'all your eggs in one basket' phrase, so I agree that running at least one instance of a service physically could be justified, but threat actors will be trying to time execution of attacks against both if possible. Adding complexity works both ways here.

I don't really agree with the comments about not patching however. The premise that the physical workload or instance would be patched or updated more than the virtual one seems unrelated. A hesitance to patch systems is more about up time vs downtime vs breaking vs risk in my opinion.

Is your organization running critical workloads virtual like anything else, combination physical and virtual, or combination of all previous plus cloud solutions (off prem)?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 month ago (1 children)

How you keep the air gapped system in sync?

[–] [email protected] 3 points 1 month ago (1 children)

We don't. It's a separate, simplified system that only lets the core team members access the layout-, editing- and typesetting-software that is locally installed on the bare metal servers.
In emergency mode, they get written articles and images from the reporters via otherwise unused, remotely hosted email addresses, and as a second backup, Signal.
They build the pages from that, send them to the printers, and the paper is printed old-school using photographic plates.

[–] [email protected] 2 points 1 month ago (1 children)

That's a very high degree of BCDR planning, and quite costly I assume.

[–] [email protected] 2 points 1 month ago* (last edited 1 month ago)

It's less than the cost of our cybersecurity insurance, which will probably drop us on a technicality when the day comes.
And it's not entirely an economic decision. The paper is family-owned in the 3rd generation, historically relevant as one of the oldest papers in the country, and absolutely no one wants to be the one in charge when it doesn't print for the first time ever.