13.11.2019 Views

code_of_practice_V3_2019

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6.10.4 Provision shall be made to protect systems against:<br />

n intentional or unintentional viruses or unauthorised Code (Cyber Security is covered in more detail at<br />

paragraph 11.6);<br />

n unauthorised installation, change, or deletion <strong>of</strong> s<strong>of</strong>tware or associated data;<br />

n the installation or use <strong>of</strong> unauthorised s<strong>of</strong>tware, (e.g. running games or <strong>of</strong>fice applications);<br />

n modification <strong>of</strong> the s<strong>of</strong>tware function by additional or modified physical devices.<br />

6.10.5 The system safety justification shall be developed to include the risks posed by the use <strong>of</strong> s<strong>of</strong>tware both afloat<br />

and ashore and how those risks are reduced to an acceptable level. Consideration should be given to conducting<br />

a Failure Mode Effects and Criticality Analysis (FMECA) to identify risks or safety Critical S<strong>of</strong>tware elements. Any<br />

function <strong>of</strong> a MASS should be adequately validated in accordance with its consequence to safety and performance<br />

<strong>of</strong> the MASS, and any s<strong>of</strong>tware implementation <strong>of</strong> this function adequately verified.<br />

6.10.6 The configuration status <strong>of</strong> the s<strong>of</strong>tware on each platform shall be captured and recorded, and the record<br />

maintained up-to-date for the life <strong>of</strong> the platform.<br />

6.10.7 The development and testing <strong>of</strong> changes to the s<strong>of</strong>tware and data, including specific arrangements for on-board<br />

testing, shall be managed so that the safety <strong>of</strong> the system, sub-system or equipment is not compromised.<br />

6.10.8 The retention and release <strong>of</strong> earlier versions <strong>of</strong> s<strong>of</strong>tware shall be managed to enable restoration <strong>of</strong> a previous<br />

known and trusted state when necessary.<br />

6.10.9 The release and installation <strong>of</strong> s<strong>of</strong>tware to each platform shall be appropriately and actively managed so<br />

that changes to s<strong>of</strong>tware are controlled. The installation process shall include a strategy for managing a failed<br />

installation.<br />

6.11 IN-SERVICE REQUIREMENTS<br />

6.11.1 Independent verification should be undertaken to provide assurance that the MASS complies in all respects with<br />

the provisions <strong>of</strong> this Code and remains compliant throughout its life.<br />

6.11.2 Construction surveys should be conducted at a periodicity and scope appropriate to the design and build and<br />

may include:<br />

n A review <strong>of</strong> the capability, organisation and facilities <strong>of</strong> the manufacturer to confirm that acceptable standards<br />

can be achieved for the construction, and fit out <strong>of</strong> the hull structure, systems and equipment;<br />

n Certification <strong>of</strong> s<strong>of</strong>tware, equipment and components;<br />

n Survey <strong>of</strong> the material state during build to confirm compliance with the appraised design;<br />

n Witness <strong>of</strong> tests and trials to demonstrate functionality;<br />

n Details <strong>of</strong> s<strong>of</strong>tware integrity testing and cyber-security compliance audits.<br />

6.11.3 Through life survey activities should be conducted at a periodicity appropriate to the design, construction, material<br />

state and operation <strong>of</strong> the MASS.<br />

46<br />

MASS UK Industry Conduct Principles and Code <strong>of</strong> Practice Version 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!