Skip to content

n-1 Bug: PCM Analysis does not follow the original specification #78

@sebinside

Description

@sebinside

The current version of the PCM-based analysis does not follow to original specification from here. Violations of confidentiality requirements are found one data flow diagram node, i.e., one entry in the action sequence to early, i.e., in node n - 1. This becomes visible when comparing the PCM-based analysis with the vanilla DFD analysis.

The original specification states: "The label comparison function compares the classification label of incoming data with the clearance label of the receiving node." (p. 97). This can happen because we do not generate an exit node for SEFFs, so the check happens "implicitly" on the out pin of the node n - 1.

TL;DR, we propose two changes:

  • Add the generation of SEFF exit nodes, see p. 174
  • The constraint should be evaluated on the state of the input pin, not the output pin

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingresearchInvestigation or reserach related issue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions