Web Infrastructure Model - Revision history

Tom: /* Solutions */

2023-12-17T00:43:55Z

‎Solutions

2023-12-17T00:35:18Z

‎Problems

2023-12-16T23:32:57Z

‎Problems

2023-12-16T21:33:07Z

‎Problems

2023-12-16T20:02:33Z

‎Problems

2023-12-16T19:21:28Z

‎Problems

2023-12-16T19:18:41Z

‎Problems

2023-12-16T19:17:37Z

2023-12-16T19:14:04Z

‎Problems

2023-12-16T19:08:09Z

‎Problems

@@ Line 50: / Line 50: @@
 ==Solutions==
-The history-based solution of the attack model used by military planners for defense against attack. Gather all of the information from the NIST archives and determine if your solution will defend against them. That is a summation of the history-based approach to threat modeling. There is another approach, however, capability-based threat modeling. What attacks will adversaries whom I reasonably expect to encounter mount once the system I am developing is deployed? Military planners call this the "responsive threat." There are many famous failures of history-based threat modeling: tanks vs. cavalry, bombers vs. battleships, vacuum tubes vs. electromechanical cipher machines, box cutters vs skyscrapers, etc. A very nice distinction.  The problem with this approach is that it depends heavily on the notion of "reasonably expect," which is highly obvious, after the fact.
+The history-based solution of the attack model used by military planners for defense against attack. Gather all of the information from the NIST archives and determine if your solution will defend against them. That is a summation of the history-based approach to threat modeling.
 ==References==

@@ Line 48: / Line 48: @@
 * Users have [[Identifier]]s, but no other [[Attribute]]s, [[Behavior]]s, etc.
 * Attacks against the browser, including plug-ins are not addressed.
 ==References==

@@ Line 43: / Line 43: @@
 ==Problems==
-* The model conflates [[Identity]] and [[Identifier]] so it is hard to understand what is at risk.
+* The model conflates [[Identity]] and [[Identifier]] so it is hard to understand what is at risk for the users of the system. In general it seems that user concerns are entirely lacking from the entire process.
 * The model is designed to deter attacks which is a backward-looking protection, not forward-looking where the new attacks will be coming from. This does not mean that protecting form existing attack is not important, just not enough.
 * The model has no notion of time, so tokens never expire, e.g., id tokens.

@@ Line 44: / Line 44: @@
 ==Problems==
 * The model conflates [[Identity]] and [[Identifier]] so it is hard to understand what is at risk.
-* The model is designed to deter attacks which is a backward-looking protection, not forward-looking where the new attacks will be coming from.
+* The model is designed to deter attacks which is a backward-looking protection, not forward-looking where the new attacks will be coming from. This does not mean that protecting form existing attack is not important, just not enough.
 * The model has no notion of time, so tokens never expire, e.g., id tokens.
 * Users have [[Identifier]]s, but no other [[Attribute]]s, [[Behavior]]s, etc.

@@ Line 44: / Line 44: @@
 ==Problems==
 * The model conflates [[Identity]] and [[Identifier]] so it is hard to understand what is at risk.
 * The model has no notion of time, so tokens never expire, e.g., id tokens.
 * Users have [[Identifier]]s, but no other [[Attribute]]s, [[Behavior]]s, etc.

@@ Line 1: / Line 1: @@
-The oigin of the [[Web Infrastructure Model]] is described in of the WIM.<ref>D. Fett, R. Kuesters, G. Schmitz. The Web SSO Standard OpenID Connect: In-Depth Formal Security Analysis and Security Guidelines. arXiv:1704.08539. type: article. arXiv,
+The origin of the [[Web Infrastructure Model]] is described in the formal review of the [[Verifiable Credential]] exchange protocols.<ref>D. Fett, R. Kuesters, G. Schmitz. The Web SSO Standard OpenID Connect: In-Depth Formal Security Analysis and Security Guidelines. arXiv:1704.08539. type: article. arXiv,
 Apr. 27, 2017. arXiv: 1704.08539[cs]. url: http://arxiv.org/abs/1704.08539 (</ref> A detailed formal description of the WIM can be found in [7]. The WIM
 is a Dolev-Yao (DY) style model that closely models existing web standards such as HTTP and HTML.