Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security markings #32

Open
CDietleinNTIA opened this issue May 3, 2022 · 0 comments
Open

Security markings #32

CDietleinNTIA opened this issue May 3, 2022 · 0 comments

Comments

@CDietleinNTIA
Copy link
Member

Suggest adding the ability to more granularly control the level of security/sensitivity of information in metadata, and the ability to differentiate the security level of (for example) an IQ .sigmf-data file vs. its corresponding .sigmf-meta.

Potential ideas:

  • Separate namespace to make machine reading simpler
  • classification becomes meta_classification (highest in the file) and only exceptions to it (lower classifications) must be marked, although anything can be marked
  • Hierarchical classification, e.g., meta_classification applies to everything and is overruled by classification at the object level
  • New data_classification (required) to specify classification of .sigmf-data file
  • Add a paragraph at the bottom of the main SigMF-NS-NTIA page that mentions this, once implemented
  • Add a simple example in ntia-core section 4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant