demo.xlsx

[ashrafkadri-va]

compliance-trestle-demos/trestle_task_spread_sheet_to_component_definition/demo.xlsx

How is the demo.xlsx file created?

[degenaro]

Presently, the input spread sheet demo.xlsx was built by hand.

[ashrafkadri-va]

Is there a logic or guidance to create demo.xlsx sheet?

[ashrafkadri-va]

Does anyone know how to create demo.xlsx sheet manually?

[ashrafkadri-va]

Are there any paid consultants for trestle tools to help us?

[degenaro]

Hello, I'd like to help but do not understand what you are trying to do. The demo you reference takes a human created spread-sheet (demo.xlsx) and makes a transformation to an OSCAL component definition. It is presumed that the user knows how to create a spread-sheet using one of the various tools available, such as Microsoft Excel. Can you say with more specificity what you are trying to accomplish? Lou.

…

On Thu, Sep 22, 2022 at 7:13 PM ashrafkadri-va ***@***.***> wrote: Are there any paid consultants for trestle tools to help us? — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD66XM2S5XU2A27BKBEEPTV7TRY7ANCNFSM6AAAAAAQGLHAL4> . You are receiving this because you commented.Message ID: ***@***.***>

[degenaro]

(venv.trestle-develop) degenaro:trestle-workspace$ trestle task xlsx-to-oscal-cd -i trestle.core.commands.task:101 WARNING: Config file was not configured with the appropriate section for the task: "[task.xlsx-to-oscal-cd]" Help information for xlsx-to-oscal-cd task. Purpose: From spread sheet and catalog produce OSCAL component_definition file. Configuration flags sit under [task.xlsx-to-oscal-cd]: catalog-file = (required) the path of the OSCAL catalog file. spread-sheet-file = (required) the path of the spread sheet file. work-sheet-name = (required) the name of the work sheet in the spread sheet file. column "ControlId" contains control ID. column "ControlText" contains control text. columns "NIST Mappings" contain NIST control mappings. column "ResourceTitle" contains component name. column "goal_name_id" contains goal name. column "goal_version" contains goal version. column "rule_name_id" contains rule name. column "rule_version" contains rule version. column "Parameter [optional parameter]" contains parameter name + description, separated by newline. column "Values default , [alternatives]" contains parameter values. output-dir = (required) the path of the output directory for synthesized OSCAL .json files. output-overwrite = (optional) true [default] or false; replace existing output when true. filter-column = (optional) column heading of yes/no values; process only "yes" rows. profile-type = (optional) one of ['by-goal', 'by-rule', 'by-control', 'by-check']

…

On Thu, Sep 8, 2022 at 12:07 PM ashrafkadri-va ***@***.***> wrote: Is there a logic or guidance to create demo.xlsx sheet? — Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD66XIVAKRTBAGWSWTUP63V5IFNDANCNFSM6AAAAAAQGLHAL4> . You are receiving this because you commented.Message ID: ***@***.***>