Defense strategy (computing): Difference between revisions

Merged the two "Unavoidable actions" subsections into one
Line 13: Line 13:


This strategy's success is based on competition of offence and defence. This is a time and resource-consuming strategy, affecting performance. The scope is variable in time. It cannot be fully successful if not supported by other strategies.
This strategy's success is based on competition of offence and defence. This is a time and resource-consuming strategy, affecting performance. The scope is variable in time. It cannot be fully successful if not supported by other strategies.
=== Unavoidable actions ===
Unavoidable actions employ security measures that cannot be prevented or neutralized. This strategy is based on the assumption that the system has been penetrated, but an intruder cannot prevent the defensive mechanism from being employed. Examples of this strategy include [[reboot]]ing, using [[physical unclonable function]]s, and using a [[security switch]].


=== Secure enclave ===
=== Secure enclave ===
Line 58: Line 55:


=== Unavoidable actions ===
=== Unavoidable actions ===
Unavoidable actions employ security measures that cannot be prevented or neutralized. This strategy is based on the assumption that the system has been penetrated, but an intruder cannot prevent the defensive mechanism from being employed. Examples of this strategy include [[reboot]]ing, using [[physical unclonable function]]s, and using a [[security switch]].
This strategy can support any other strategy.<ref>{{Cite web|url=https://www.pcworld.com/article/3225913/what-is-two-factor-authentication-and-which-2fa-apps-are-best.html|title=What is two-factor authentication, and which 2FA solutions are best?|date=June 5, 2019|website=PCWorld}}</ref><ref>{{Cite web|url=https://www.researchgate.net/figure/A-PUF-Based-Encryption-Scheme_fig3_314296637|title=PUF based encryption|website=www.researchgate.net}}</ref><ref>{{Cite web|url=https://hal.archives-ouvertes.fr/hal-01322882/document|title=Design and implementation of Hardware-assisted security architecture for software integrity monitoring|website=hal.archives-ouvertes.fr}}</ref><ref>{{Cite web|url=https://www.sciencedaily.com/releases/2018/02/180219141219.htm|title=Real-time Captcha technique improves biometric authentication|website=ScienceDaily}}</ref>{{clarify|date=December 2019}} This is a resource-consuming strategy, and the scope is determined by the designer. An implementation may have a wide impact on devices.<ref>{{Cite web|url=https://amosbbatto.wordpress.com/2019/08/15/adding-switches-not-simple/|title=Adding kill switches to protect your privacy is not as simple as you might think|website=amosbbatto.wordpress.com|date=August 15, 2019}}</ref> This strategy can be fully successful, but in most cases, there is a trade-off of full system functionality for security. This strategy can be used [[proactive]]ly or reactively. Actions done in response to an already detected problem may be too late.<ref>{{Cite web|url=https://arstechnica.com/cars/2019/10/should-all-connected-cars-have-a-physical-network-kill-switch/|title=Should all connected cars have a physical network kill switch?|first=Jonathan M.|last=Gitlin|date=October 18, 2019|website=Ars Technica}}</ref> Any implementation needs to be supported by the secure enclave strategy in order to prevent neutralizing action by unauthorized access to the protection mechanism.
This strategy can support any other strategy.<ref>{{Cite web|url=https://www.pcworld.com/article/3225913/what-is-two-factor-authentication-and-which-2fa-apps-are-best.html|title=What is two-factor authentication, and which 2FA solutions are best?|date=June 5, 2019|website=PCWorld}}</ref><ref>{{Cite web|url=https://www.researchgate.net/figure/A-PUF-Based-Encryption-Scheme_fig3_314296637|title=PUF based encryption|website=www.researchgate.net}}</ref><ref>{{Cite web|url=https://hal.archives-ouvertes.fr/hal-01322882/document|title=Design and implementation of Hardware-assisted security architecture for software integrity monitoring|website=hal.archives-ouvertes.fr}}</ref><ref>{{Cite web|url=https://www.sciencedaily.com/releases/2018/02/180219141219.htm|title=Real-time Captcha technique improves biometric authentication|website=ScienceDaily}}</ref>{{clarify|date=December 2019}} This is a resource-consuming strategy, and the scope is determined by the designer. An implementation may have a wide impact on devices.<ref>{{Cite web|url=https://amosbbatto.wordpress.com/2019/08/15/adding-switches-not-simple/|title=Adding kill switches to protect your privacy is not as simple as you might think|website=amosbbatto.wordpress.com|date=August 15, 2019}}</ref> This strategy can be fully successful, but in most cases, there is a trade-off of full system functionality for security. This strategy can be used [[proactive]]ly or reactively. Actions done in response to an already detected problem may be too late.<ref>{{Cite web|url=https://arstechnica.com/cars/2019/10/should-all-connected-cars-have-a-physical-network-kill-switch/|title=Should all connected cars have a physical network kill switch?|first=Jonathan M.|last=Gitlin|date=October 18, 2019|website=Ars Technica}}</ref> Any implementation needs to be supported by the secure enclave strategy in order to prevent neutralizing action by unauthorized access to the protection mechanism.