Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File integrity checks. #133

Open
colek42 opened this issue Sep 29, 2021 · 1 comment
Open

File integrity checks. #133

colek42 opened this issue Sep 29, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@colek42
Copy link
Member

colek42 commented Sep 29, 2021

in-toto only calculates the hash of the file on disk, and does not know what data is actually loaded into memory. Both Windows and Linux have methods to verify the integrity of the files loaded into memory

Linux:

The IMA log when the ima_policy=tcb records hashes of all the files loaded into memory

GRUB_CMDLINE_LINUX="ima_policy=tcb ima_hash=sha256 ima=on"

TPM 2.0 PCR Register 10 stores the Aggregate SHASUM of the IMA Log.

These can be used to verify that the files on disk, which in-toto hashes, actually match what was in memory when the code was compiled.

The following screenshot shows the IMA log after running an exploit tool

Screenshot from 2021-09-28 23-18-24

Windows:
Windows should be a separate effort. I do believe there is an event log that we can verify with the TPM.

https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/switch-pcr-banks-on-tpm-2-0-devices

@colek42 colek42 added the enhancement New feature or request label Sep 29, 2021
@shibumi
Copy link
Collaborator

shibumi commented Sep 29, 2021

This looks really good already. Is there anything we can help with or support you?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants