threat-modeling

"AA03": { "description": "Weakness in SSO Authorization", "source": (Process, Element), "target": (Process, Server), "condition": "target.implementsAuthenticationScheme is False", },

What if the Process implements BasicAuth or uses mutual TLS (neither of which is SSO)?
If the Process uses SAML or OAuth, then maybe.
Maybe authenticationScheme as a string var is neces

Describe the bug
This will be a tracker issue for any of the further PRs I make to fix small CSS fixes.

• The threat dragon mascot's size is not responsive and goes out of the screen for various devices!

Any additional context, screenshots, etc
If you also find any such bug and would like it to be fixed, feel free to comment below and I'll take a look at it!

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Version of CAIRIS

Details of browser or, if applicable, details of the OS used to host CAIRIS

After every player has passed, but before a new card has been drawn, the "Remove Threat" button is still clickable.
The UI suggests that everything is ok, but the threat does not get removed in this corner case.

I believe it is due to

if (hasPlayerPassed(G, ctx) || (threat.owner !== ctx.playerID)) {
  return INVALID_MOVE;
}

in deleteThreats() in moves.js. One is still at