Add correlation to BSL-docs

[jeronstone]

This is documentation for NASA-AMMOS/BSL#334 and NASA-AMMOS/BSL#340.

[BrianSipos]

The definitions of correlation don't explain how they relate to role. Are they valid only on source role? What happens if a correlation is given for rules of other roles? This may need a patch on the library if the property is forbidden for other roles.

[jeronstone]

The definitions of correlation don't explain how they relate to role. Are they valid only on source role? What happens if a correlation is given for rules of other roles? This may need a patch on the library if the property is forbidden for other roles.

This is a good consideration.

In BSL, if correlation is set in the SecOp for verif/accept, it should have no affect at the moment. So, it's not necessarily "bad" if correlation is set for those roles, but I agree we should specify here that it is for source role.

I think for now we can patch the policy parser to warn that correlation on non-source roles will do nothing.

[BrianSipos]

Suggestion for clarity of use.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud