Pattern Hum-iSH-LnS+LnS should be in package#Network

[mike1813]

Construction pattern Hum-iSH-LnS+LnS adds a LoginService controlling any ShellHost that is managed by a Human who does not interactWith the ShellHost, i.e., they can't use a physical terminal to login and administer the ShellHost.

This should be a package#Network inference, but the pattern contains a prohibited isPod link, and isPod is a package#CloudManagement feature, so that dependency forces Hum-iSH-LnS+LnS to also be in package#CloudManagement.

Possible solutions could be:

1. Make isPod a package#Network feature, though this would be odd as it indicates a Host is a Pod, and Pod should be in package#CloudManagement.
2. Remove the Pod class from the list of subclasses of a SimpleHost, so it is no longer considered a ShellHost.

The second option seems like the best one, but SimpleHost is used in other construction patterns and threats. It would be necessary to review these, and create extra patterns or threats for Pod class assets where previously they were included in the SimpleHost versions.

[mike1813]

The same issue arises in VH-LnS+LnS, which should be package#Virtualisation not package#CloudManagement. The solution here could be to replace VH-LnS+LnS by others patterns specific to the types of virtual host that have remote login (the approach used for physical hosts in PC-LnS+LnS, Rr-LnS+LnS and Sv-LnS+LnS).

Also in subsequent patterns Pc-hSHLnS+c and Hum-iHRAS+i, which should also be package#Network. In both cases it should be OK just to delete the isPod link because both are triggered only if there is a remote access service on the Host. There is a case for creating a modelling error that a Pod can't host a RemoteAccessService, just in case a user asserts this.