Paper on mitigation of IT risks

In my work in the digital sovereignty working group of the German Gesellschaft für Informatik, I created a paper outlining the typical risks we are confronted with using standard proprietary IT systems like Windows and possibilities for mitigating these risks, including the use of Qubes OS.

The paper is structured as follows:

1 Awareness of the risks of IT use
2 Vulnerabilities and risks
3 Causes and originators of threats
4 Improving technical protection
5 Necessary changes in IT usage
6 Conclusion

If you are interested, please have a look at it:

IT-Risks_and_Sovereignty_V3_0 en-US.pdf.gz (94.6 KB)

I would greatly appreciate any comments!

12 Likes

You consider use cases within SMB and enterprises?

In order to make QubesOS suitable business solution, we must have option for central management of dom0’s over different devices for remote audit, backups and security management.
Any type of such solution compromise QubesOS security model.

Except of a situation when QubesOS used by IT system administrator as his own endpoint to isolate management interfaces from remote support connections for example.
But he should take personal responsibility in all aspects of his QubesOS device.

Nice, do you have an official paper on this with DOI number and so on, so it could be quoted?

It’s still a work in progress, and we are considering where to put it finally. And still, further changes may occur if someone in the working group becomes active.

Qubes Air Zones

with multi user environment

1 Like

I have a question about your description of Qubes here:

Use of application software in separate virtual machines that receive their soft-
ware as copies from their assigned templates when they start up and whose soft-
ware is destroyed again when they shut down, so that no malware can be permanently installed there

(Honestly, this probably isn’t the best place to ask this, but this is what piqued my curiosity about this feature)

Your claim here is that no malware can persist because software is destroyed upon shutting down the VM. But what if the malware is, for instance, an App Image or a file? Then malware can definitely persist in those cases, no?

Then use disposables. And don’t install appimages.
You can run qubesos almost entirely in ram.
There is guide about it.

I was pointing out his description of AppVMs, which seems to claim malware can’t persist.

I had to simplify the description somewhat because the intended target audience probably never heard of Qubes and its template concept.

Surely, malware that’s stored somewhere in the user directories of an AppVM, like a macro virus in an office document, will survive the restart of that AppVM. However, it will remain dormant until the document is opened again, and even then, it will not be able to infect the system part of the AppVM permanently, because any data it stores there will be destroyed upon the restart of the AppVM.

The only way for malware to affect an AppVM permanently is if it resides in a document or an application stored completely in a user directory, and if that document is opened automatically or the application is started automatically whenever the AppVM is started. But I guess that is a rather exotic situation that should never occur in the careful usage of AppVMs. Still, even in that situation, the infection will be restricted to this one AppVM and will not be able to propagate into other VMs, especially not into a template.

Here, I have to stress the importance of the advice of @KitsuneNoBaka to avoid appimages, which, by their concept, are a clear violation of the separation of user data from system structures, and therefore should never be used if you want to rely on the protection provided by the template concept.

1 Like

It depends from what you are mean with “install” of malware. If you mean, that malware is persisted as file somewhere in the users home folder, yes.
If you mean “install in the system, so that it can infect other system parts or other users and started automatically, when the system starts”, then no.
I think, the second description fits the traditional meaning of “computer virus” or “malware” better then the first.
Of course, Qubes OS cannot protect you from incidents like “Glassworm” or “Shai Hulud”, but that fact is shared with almost all other Operating Systems.
Every place, that a user can write to is potentially a place, where unfriendly software can resist also.

2 Likes

I would specifically focus on the fact that US government agencies have SecureView licensed to them for free to be used in high risk environments, and it is proprietary. Qubes fills this gap for Europe like a charm.

1 Like

PDFs are dangerous. Why not plain text? Or markdown if you want a little formatting.

1 Like