From 3fcea8ade09f68f79f9675e63872842aaa4b254b Mon Sep 17 00:00:00 2001 From: Arthur Grisel-Davy Date: Sun, 25 Jun 2023 22:11:58 -0400 Subject: [PATCH] statement incoherent IDS --- BPV/qrs/main.typ | 3 +++ 1 file changed, 3 insertions(+) diff --git a/BPV/qrs/main.typ b/BPV/qrs/main.typ index a46a817..acb167c 100644 --- a/BPV/qrs/main.typ +++ b/BPV/qrs/main.typ @@ -105,6 +105,9 @@ The integrity verification can also be performed at run-time as part of the firm The above solutions to firmware attacks share the common flaw of being applied to the same machine they are installed on. This allows an attacker to bypass these countermeasures after infecting the machine. An attacker that could avoid triggering a verification, tamper with the verification mechanism, feed forged data to the verification mechanism, or falsify the verification report could render any defense useless. +//This idea of necessary independence between target and the @IDS can be summarize with teh following statement.\ +//#align(center,text(weight: "bold", [An @IDS is incoherent if its deployement requires the cooperation of the entity it pretends to protect.])) + @IDS are subjected to a trade-off between having access to relevant and meaningful information and keeping the detection mechanism separated from the target machine. Our solution addresses this trade-off by leveraging side-channel information.