Bug 122653 - make Classification policy file example.xml more instructive and complete
Summary: make Classification policy file example.xml more instructive and complete
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.0.0.alpha0+
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Classification
  Show dependency treegraph
 
Reported: 2019-01-11 13:14 UTC by Cor Nouws
Modified: 2020-02-17 10:50 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cor Nouws 2019-01-11 13:14:41 UTC
The Classification configuration file providing the configuration, example.xml, gives the content for the Classification dialog and for handling severity levels.
- The examples and content can be more instructive, recognizable for also organizations working with TSCP.
- Furthermore start using FIPS-199 for the impact level, having clear levels Low, Moderate, High (in stead of 0,1,2,3 as with the UK-Cabinet scale).
- Also add all scale impact types to the example.xml file – though current code only evaluates Confidentiality.
Comment 1 Cor Nouws 2019-01-11 13:16:43 UTC
will provide a patch for international (English) example.xml and the Dutch one.
And after applying inform the l10n list to give others the opportunity to change or even translate.
Comment 2 Cor Nouws 2019-01-11 13:35:36 UTC
patch https://gerrit.libreoffice.org/66169
Comment 3 Cor Nouws 2019-01-11 13:39:15 UTC
(In reply to Cor Nouws from comment #0)
Also done:
- add usable example markings and part numbers, showing up in the dialog
Comment 4 Xisco Faulí 2019-06-10 14:59:20 UTC
(In reply to Cor Nouws from comment #2)
> patch https://gerrit.libreoffice.org/66169

Restored in gerrit
Comment 5 Xisco Faulí 2019-09-26 10:23:05 UTC
(In reply to Xisco Faulí from comment #4)
> (In reply to Cor Nouws from comment #2)
> > patch https://gerrit.libreoffice.org/66169
> 
> Restored in gerrit

restored again
Comment 6 Xisco Faulí 2020-02-17 10:50:15 UTC
Dear Cor Nouws,
This bug has been in ASSIGNED status for more than 3 months without any
activity. Resetting it to NEW.
Please assign it back to yourself if you're still working on this.