-
Key: SACM-21
-
Legacy Issue Number: 16695
-
Status: closed
-
Source: Adelard LLP ( Luke Emmet)
-
Summary:
: In the Industrial Press example, the attribute toBeSupported=”True” should be present in element 9, C2.3. This is reflected by the presence of a diamond in the GSN portrayal on page 23, Figure 3.
-
Reported: SACM 1.0b1 — Fri, 18 Nov 2011 05:00 GMT
-
Disposition: Resolved — SACM 1.0b2
-
Disposition Summary:
Replace the content of B.1 with the following
<?xml version="1.0" encoding="ASCII"?>
<SACM:Argumentation xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SACM="SACM" xmi:id="0">
<containsReasoningElement xsi:type="SACM:Claim" xmi:id="1" identifier="C1" description=""
content="C/S logic is fault free"/>
<containsArgumentElement xsi:type="SACM:ArgumentReasoning" xmi:id="2" identifier="RC1.1"
content="Argument by omission of all identified software hazards" describes="5 6"/>
<containsArgumentElement xsi:type="SACM:ArgumentReasoning" xmi:id="3" identifier="RC1.2"
content="Argument by satisfaction of all C/S safety requirements" describes="7 8 9"/>
<containsArgumentElement xsi:type="SACM:InformationElement" xmi:id="4" identifier="IRC1.1"
description="Identified software hazards"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="5" identifier="C1.1" description=""
content="Unintended opening of press (after PoNR) can only occur as a result of component failure"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="6" identifier="C1.2" description=""
content="Unintended closing of press can only occur as a result of component failure"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="7" identifier="C2.1" content="Press
controls being 'jammed on' will cause press to halt"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="8" identifier="C2.2" content="Release of
controls prior to press passing physical PoNR will cause press operation to abort"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="9" identifier="C2.3" description=""
content="C/S fails safe (halts on) and annunciates (by sounding Klaxon) all component failures"
toBeSupported=”TRUE”/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="12" identifier="C2.1.1" content="Failure 1
of PLC state machine includes BUTTON_IN remaining true"/>
<containsArgumentElement xsi:type="SACM:Claim" xmi:id="13" identifier="C2.2.1" content="Abort
transition of PLC state machine includes BUTTON_IN going false"/>
<containsArgumentElement xsi:type="SACM:InformationElement" xmi:id="10" identifier="S1.1"
content="Fault tree analysis cutsets for event 'Hand trapped in press due to command error'"/>
<containsArgumentElement xsi:type="SACM:InformationElement" xmi:id="11" identifier="S1.2"
content="Hazard directed test results"/> <containsArgumentElement xsi:type="SACM:InformationElement" xmi:id="14" identifier="S2.1"
description="" content="black box testing"/>
<containsArgumentElement xsi:type="SACM:InformationElement" xmi:id="15" identifier="S2.2.1"
content="C/S state machine"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="16" identifier="C1.1.1"
description="" source="5" TARGET="1"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="17" identifier="C1.1.2"
source="6" TARGET="1"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="18" identifier="C1.2.1"
source="7" TARGET="1"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="19" identifier="C1.2.2"
source="8" TARGET="1"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="20" identifier="C1.2.3"
source="9" TARGET="1"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" xmi:id="21" identifier="CIRC1.1"
source="4" TARGET="2"/>
<containsAssertedRelationship xsi:type="SACM:AssertedEvidence" xmi:id="22" identifier="S1.1"
source="10" TARGET="5 6"/>
<containsAssertedRelationship xsi:type="SACM:AssertedEvidence" xmi:id="23" identifier="S1.2"
source="11" TARGET="5 6"/>
<containsAssertedRelationship xsi:type="SACM:AssertedEvidence" xmi:id="24" identifier="SC2.1"
source="14" TARGET="7"/>
<containsAssertedRelationship xsi:type="SACM:AssertedEvidence" xmi:id="25" identifier="SC2.1.1"
source="15" TARGET="12"/>
<containsAssertedRelationship xsi:type="SACM:AssertedEvidence" xmi:id="26" identifier="SC2.2.1"
source="15" TARGET="13"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="27" identifier="DI C2.1"
source="12" TARGET="7"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" xmi:id="28" identifier="DI C2.2"
source="13" TARGET="8"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" xmi:id="29" identifier="AR29"
source="2" TARGET="16 17"/>
</SACM:Argumentation>
Replace the content of B.2 with the following
<?xml version="1.0" encoding="ASCII"?>
<SACM:Argumentation xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SACM="SACM" identifier="BSC11">
<containsArgumentElement xsi:type="SACM:Claim" identifier="Bluetooth secure" content="A bluetooth
enabled network provides adequate security"/> <containsArgumentElement xsi:type="SACM:Claim" identifier="Availability" content="A bluetooth enabled
network is adequately available [1] Section 1 para 3"/>
<containsArgumentElement xsi:type="SACM:Claim" identifier="Access" description="" content="A
bluetooth enabled network provides adequate control for access to services and data [1] Section 1 para 3"/>
<containsArgumentElement xsi:type="SACM:Claim" identifier="Confidentiality" content="A bluetooth
enabled network provides adequate levels of confidentiality [1] Setion 1 para 3"/>
<containsArgumentElement xsi:type="SACM:Claim" identifier="Integrity" content="A bluetooth enabled
network provides adequate levels of integrity [1] Section 1 para 3"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="Context: security policy and
scenario for use" content="Definitions are required of the intented security policy and the scenario of use for
the system, including what is regarded as 'adequate'"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="References" content="[1]
Bluetooth security white paper 19/4/02"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="Definition: Availability"
content="The system is capable of providing requested services to authorised users, in an
acceptable/defined time"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="Definition: Access"
content="Only users permitted by the defined security policy have access to services and data"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="Define: Confidentiality"
content="Unauthorised persons cannot intercept and understand information to which they are not
entitled"/>
<containsArgumentElement xsi:type="SACM:InformationElement" identifier="Define: Integrity"
description="" content="Services and data are provided to authorised users as intended and without
corruption"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC1" source="References"
target="Bluetooth secure"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC2" source="Context:
security policy and scenario for use" target="Bluetooth secure"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC3" source="Definition:
Availability" target="Availability"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC4" source="Definition:
Access " target="Access"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC5"
source="Define:Confidentiality" target="Confidentiality"/>
<containsAssertedRelationship xsi:type="SACM:AssertedContext" identifier="AC6" source="Define
:Integrity" target="Integrity"/>
<containsAssertedRelationship xsi:type="SACM:AssertedInference" identifier="AI1" source="Integrity
Confidentiality Access Availability" target="Bluetooth secure"/>
<containsArgumentElement xsi:type="SACM:ArgumentReasoning" identifier="Argue over vulnerabilities"
description="" content="Argue for each security requirement identified in the security white paper"
describes="AI1"/>
</SACM:Argument> -
Updated: Fri, 6 Mar 2015 20:58 GMT
SACM — ARM: Page 21, section 8.3.1
- Key: SACM-21
- OMG Task Force: Structured Assurance Case Metamodel (SACM) FTF