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.

Sign up for GitHub

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

Jump to bottom

Should not have picked up my issue 19 changes #44

Merged
merged 2 commits into from
Nov 4, 2015
Merged

Should not have picked up my issue 19 changes #44

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7cecf2
Merge remote-tracking branch 'refs/remotes/sacmwg/master'
jimsch Nov 4, 2015
68d0ed5
Remove over aggressive change
jimsch Nov 4, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 14 additions & 12 deletions draft-ietf-sacm-architecture.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -265,18 +265,20 @@ aggregated Posture Assessment Information that can be shared.</t>
to share or
provide Posture Assessment information.</t>

<t>One means by which a Provider shares information, is in response to a direct request from a Consumer.
The response can be either a single response, or a series of responses for a subscription request.
In the event of a subscription, the Provider will occassionally need to update the authorization of the Consumer.</t>

<t>A Provider may also share information spontaneously without a previous request from a Consumer.
In this case, the Provider obtain a destination and authorization via a broker or a proxy component.</t>

<t>Both the spontaneous and subscription cases support use cases where asynchronous publication of
a change in a posture state requires that the Provider
provide the change to Consumers (such as Security Information and Event Management (SIEM) system);
similarly, SIEM applications that are providing live information require
such updates to posture information to be provided asynchronously.</t>
<t>One means by which a Provider shares information, is in response to a direct request from a Consumer.</t>

<t>
A Provider may also share information spontaneously. Use cases such
as the change in a posture state require that a Provider be able to
provide such changes or updates especially to Consumers such as
Security Information and Event Management (SIEM) systems; similarly,
SIEM applications that are providing live information require any
such updates or changes to posture information to be provided
spontaneously. Authorization for the enabling for these unsolicited
messages happens through the Controller at the time that both
Provider and Consumers request authorization for (spontaneous)
messages.
</t>

<t>The information provided, may be filtered or truncated to provide a
subset of the requested information to honor the request. This
Expand Down