RE: [Non-DoD Source] Re: [openc2-actuator] Firewall Profile: Purpose and Scope

["Brule, Joseph M" <jmbrule@radium.ncsc.mil>]

All,

 

I have been receiving direct replies to my queries about the firewall profile.  I want the entire email distribution to be aware of the discussions, AND I want to respect anonymity, so I ‘sanitized’ the emails and include everyone on the response. 

 

======  tear line ====

 

 

Regarding your comment to the command options comment:  The command options were defined independently of any particular action, target or actuator (that is, we are striving for decoupled components).  Having said that,  some command options do not make sense for a particular ACTION TARGET pair in the context of a specific ACTUATOR, therefore the actuator profile identifies the applicable components. 

 

VR

 

Joe B

 

To: Brule, Joseph M <jmbrule@radium.ncsc.mil>
Subject: [Non-DoD Source] Re: [openc2-actuator] Firewall Profile: Purpose and Scope

 

Joe,

 

 

 

I think these are pretty accurate, I have one comment and that is related to the "command options" comment. I was always under the impression that command options where independent of a given actuator profile, I guess I figured any options associated to an actuator would fall under actuator options.

 

 

 

V/R

 

On Tue, Apr 3, 2018 at 9:03 AM, Brule, Joseph M <jmbrule@radium.ncsc.mil> wrote:

Actuator Profile Subcommittee,

This probably should have been the first email I sent....

We will spend a lot of time talking past each other if we do not have a common understanding of the purpose and scope.  Please review the following ten bullets.  If you do not agree, please identify which one(s), why, and ideally provide alternate text.

*    Identify the OpenC2 ACTIONS that are applicable to the actuators with firewall functionality.
*    Identify the TARGET types and associated specifiers that are applicable to each action in the firewall class of actuators.
*    Identify ACTUATOR SPECIFIERS,   ACTUATOR-OPTIONS and COMMAND OPTIONS for each action-target pair that are applicable and/or unique to the firewall class of actuators
*    Annotate each Action/ Target pair with a justification and example and provide sample OpenC2 commands to a firewall
*    Provide an abstract schema that captures the specifiers and options for a firewall

*    Does not define or implement ACTIONS external to Version 1.0 of the Language Specification.
*    Is conformant with version 1.0 of the OpenC2 Language Specification
*    Defines the required and optional ACTIONS and OPTIONS.
*    Defines the applicable TARGETS utilizing the target data model provided in version 1.0 of the OpenC2 Language this specification..
*    Defines the required and optional actuator 'specifiers'.

Thank you

Joe B

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php