3 ms·
What are the tradeoffs to something like this? What attack vectors are still present and what attack vectors does this prevent? Thanks, cool project!
by sleno 2y ago
What are the tradeoffs to something like this? What attack vectors are still present and what attack vectors does this prevent? Thanks, cool project!
- jgiraldo29 2y agoThank you so much. Now let me break this questions down: Key Security Benefits: 1. Cryptographic Verification: - Prevents silent corruption of system state - Makes tampering with system logs cryptographically difficult - Provides verifiable audit trails of all system operations - Enables detection of hardware memory faults 2. Runtime Integrity: - Prevents invalid memory access patterns - Ensures filesystem operations maintain consistency - Verifies process state transitions - Guards against buffer overflows in key subsystems Main Tradeoffs: 1. Performance Impact: - 3-5% overhead for memory operations - 7-9% overhead for filesystem operations - Additional storage needed for proof chains - Increased memory usage for verification structures 2. Complexity: - More complex memory management - Additional failure modes to handle - Higher system initialization overhead - More complex recovery procedures Attack Vectors Still Present: - Physical hardware attacks (DMA, cold boot) - Side-channel attacks - Race conditions (though reduced by verification) - Attacks that operate within valid operation boundaries - Core CPU/firmware-level vulnerabilities Attack Vectors Prevented/Mitigated: - Memory corruption exploits - Filesystem integrity attacks - Unauthorized state transitions - Historical state tampering - Many types of privilege escalation Im actively working on making the other attack vectors disappear as a whole. It's quite extensive as it is, so it's got a lot of things packed on it. ( * ´ ω ｀ * )