Revised Data Collection Prototype Slides

[Charles Schmidt]

Hi all,

Attached are the revised slides for the Data Collection Prototype to discuss on today's call.

Charles

[David Kemp]

Hi all,

I converted the Data Collection Prototype slide 3 to a schema to illustrate the OpenC2 design process:

1) Starting with the message names (green), derive a Type-Name (uppercased) for each one.  Use Record as the type unless you know a different type is needed.
2) Add the attributes (orange) as fields under each type, using an attribute_name (snake_case) and Type of the attribute.  Attributes are numbered consecutively.

3) Add a stub String for each Type that has not yet been defined

And voila - you have a schema, including a JSON Schema that can be used for JSON messages used in the architecture.

I did some guessing to create this first version; you may have different ideas for appropriate type names. Feel free to change them, and observe that the intent of the green message names is to be exactly the TypeName of the message.

All of the schema files are posted in https://github.com/oasis-tcs/openc2-usecases/tree/master/SBOM-PoC/Schemas/scapv2-edc-proto.  edc.jidl is the file you want to look at and edit.  The .jadn file is the machine-readable equivalent, and the .md file is the table equivalent that we use in OpenC2 documents.

Regards,
Dave

--
To unsubscribe from this group, send email to scap-dev-endpo...@list.nist.gov
Visit this group at https://list.nist.gov/scap-dev-endpoint
---
To unsubscribe from this group and stop receiving emails from it, send an email to scap-dev-endpo...@list.nist.gov.

[Charles Schmidt]

Hi Dave,

Thank you for posting this. I (finally) took a look at this and overall I think this is a great start. Some specific comments/responses:

- You asked if Assessment-Info (in Store-Assessment-Info) is the same as Report-Results, When storing data to the Repository, a common method should be used in all cases and the only difference would be the data stored. As such, Store(Assessment Info) and Store(Results) would be the same Store method. Assessment Info is not the same as Results. The Assessment Info consists of the instructions that guide the assessment along with the specific parameters that constrain behaviors (e.g., PCE filters). The Results would be the results of the assessment. The Results would reference the Assessment Info that guided their creation and a single set of Assessment Info could be associated with many Results.

- I am not sure where Query-Info and Results-Info come from.

- Format-Filters and Collection-Parameters would be the same data type as both determine the type of result format and filters to apply to assessment results. The group has gone back and forth as to whether both are needed.

Beyond that, if you could spend some time on next week's call walking us through this in a bit more detail, I think that would be invaluable.

Thanks again for putting this together.

Charles

On Thursday, September 3, 2020 at 2:07:50 PM UTC-5, David Kemp wrote:

Hi all,

I converted the Data Collection Prototype slide 3 to a schema to illustrate the OpenC2 design process:

1) Starting with the message names (green), derive a Type-Name (uppercased) for each one.  Use Record as the type unless you know a different type is needed.
2) Add the attributes (orange) as fields under each type, using an attribute_name (snake_case) and Type of the attribute.  Attributes are numbered consecutively.

3) Add a stub String for each Type that has not yet been defined

And voila - you have a schema, including a JSON Schema that can be used for JSON messages used in the architecture.

I did some guessing to create this first version; you may have different ideas for appropriate type names. Feel free to change them, and observe that the intent of the green message names is to be exactly the TypeName of the message.

All of the schema files are posted in https://github.com/oasis-tcs/openc2-usecases/tree/master/SBOM-PoC/Schemas/scapv2-edc-proto.  edc.jidl is the file you want to look at and edit.  The .jadn file is the machine-readable equivalent, and the .md file is the table equivalent that we use in OpenC2 documents.

Regards,
Dave

On Wed, Sep 2, 2020 at 12:59 PM Charles Schmidt <schmidt...@gmail.com> wrote:

Hi all,

Attached are the revised slides for the Data Collection Prototype to discuss on today's call.

Charles

--

To unsubscribe from this group, send email to scap-dev...@list.nist.gov

Visit this group at https://list.nist.gov/scap-dev-endpoint
---

To unsubscribe from this group and stop receiving emails from it, send an email to scap-dev...@list.nist.gov.