> Should you need a step-by-step guide for drafting an ETSI deliverable, please consult the " [Principles for Drafting ETSI Deliverables](https://portal.etsi.org/Portals/0/TBpages/edithelp/Docs/Principles_for_drafting_ETSI_deliverables.pdf)" document. Otherwise you may contact us at [edithelp@etsi.org](mailto:edithelp@etsi.org).
**CAUTION: This INTERIM DRAFT document is provided for information and is for future development work within the ETSI Technical Committee CYBER Working Group EUSR only. ETSI and its Members accept no liability for any further use/implementation of this Specification. Approved and published specifications and reports shall be obtained exclusively via the ETSI Documentation Service at [http://www.etsi.org/standards-search]()**
<divstyle="text-align: center;">
**_Important notice_**
@@ -77,7 +77,7 @@ Any software contained in this deliverable is provided "AS IS" with no warrantie
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media.
@@ -702,8 +702,13 @@ How exactly this will be done is yet to be determined, but here is our proposal:
* documentation for any testing software or hardware used
* the parameters or arguments they used for the software or hardware
* any setup information for the test (load this module, flip this switch, run this script, etc.)
* The standard can include requirements for the tools used in the test itself (features or sensitivity or maybe even source code available?)
* Any tests should demonstrate both the failure and success version of the test to rule out false positives or negatives
Mitigations are how a technical requirement can be satisfied. Mitigations must be tailored to the use case and take into account the user’s sophistication and the operational environment.
