Internet Security

From MgmtWiki
Revision as of 09:44, 18 September 2021 by Tom (talk | contribs) (Solutions)

Jump to: navigation, search

Full Title or Meme

Internet Security appears to be an oxymoron as a network of networks could not be expected to harbor any underlying security model. So what ever security is to exist will need to be layered over the internet.


While the Internet may appear to be just a swamp of bad actors, as shown below, we can discuss security for two broad categories of real-world actors, the service providers and the human users. The follows graphic shows those two real-world actors, together with their digital internet manifestations and the interactions among the actors.

  1. Human user to user -This particular path is almost never used in 2020. One good experience shows why users might like to increase its use is the case of Proton Mail shared the IP address of one of its users as part of a French investigation that led to the arrest of climate activists. The exact opposite behavior as the privacy they promised at their inception and the very activity for which Phil Zimmermann created PGP.
  2. Human user to Trusted Service Provider which should be the only connection that use agents allow, if it were only possible to determine which providers were not bad actors.
  3. Service Provider to Service Provider is the type of interchange that supports user Identifier providers (IdPs) using protocols like OpenID Connect. As a point of interest the OIDC back channel is the one shown in the graphic, the front channel communications the involves the user bounces all interchanges off the user browser, only some of which are apparent to the user. This bouncing of data off the browsers is the source of the widespread user tracking that is increasingly coming under user control as a result of the propagation of the Internet Bill of Rights.
  4. Bad actor attacking users.
  5. Bad actors attacking service providers.
  • There are two interfaces of interest, (1) at the user's agent, and (2) at the provider endpoint access to the internet.
  • There is one source of trust of interest: a list of trusted service providers either in the user head or in the user's agent.
  • All security is inherent in the messages that are received from the swamp, so the structure and content of these messages, combined with the security of the digital devices, procedures and programs used by the real-world entities will be the entire determinate of the security of the site.



The shear volume of devices, software and procedures used at any digital endpoint makes securing the entirety of the endpoint very difficult. Attempts to focus on the protocols or data structures used in the interchanges over the internet have proved to be inadequate to the task.

As a first step this site will focus on the security of the user devices, in particular with the mobile smartphone both as a platform as the apps that work on that platform operating together as a user agent. This can be combined later in the project with any service providers that directly focus on user agent functions.

The complexities that can be faced in securing the operation of a user agent is well exhibited in this Louisiana Wallet example which can both protect the mobile driver's license of the holder, but also act as a verifier of other's license as might be encountered if the holder were a gig worker that had to verify the age of the recipient of, for example, a delivery of wine to the household. In this case the physical location of both smartphones, and the reason for the request (delivery of alcoholic beverages) can be known by the issuer.


Many resources exist that expound on how a server can build a secure site and the forces behind them have the assets and desire to ensure their security. The same cannot be said for the regular, human users of the internet. Very few resources are available to focus on their security above other, commercial interests. So let this site focus on those human users' internet security.

The solution proposed here is a set of security requirements for user agents holding mobile credentials which could let to a set of software assurance criteria that should be developed to enable testing of the mobile platforms and the applications running on those platforms.

Security Profile

  1. HTTPS (TLS) is used throughout the interchange which will block attackers from examining the data transferred.
  2. User authentication credentials are well protected by the user agent.
  3. If the user agent stores authentication credentials (for example in a password manager) they are not release in plain text without strong authentication of the user's presence at the device.

Privacy Profile