To test with an EDSA module in beSTORM, do the following:

  1. Open beSTORM Client.
  2. Select New Project. The beSTORM New Project Wizard opens.
  3. On the Welcome page, enter a name for the project in the Project Name box. 
  4. For Please select the wizard level, select Advanced.
  5. Select Next.
  6. On the Basic Configuration page, select an EDSA module to test with from the beSTORM's predefined modules list. This example shows the ARP (Address Resolution Protocol) as specified by [ISASecure EDSA-402] ISCI Embedded Device Security Assurance – Testing the robustness of implementations of the IETF ARP protocol over IPv4. 
  7. From the Network Device list, select the device to use for testing.
  8. Select Next.
  9. On the Advanced Configuration page, leave all parameters to their default setting.
  10. Select Next.
  11. On the Module Environment page, set various parameters related to the tests. To make any change, select the corresponding box in the Value column, and then modify its contents. For further recommendations and a full description of possible values, see the beSTORM User Guide.
  12. Select Next.
  13. On the Test Selection page, all tests are selected by default. To skip a test, clear its check box.
  14. Select Next.
  15. On the Extra Configuration page, set the Saturation Rate Threshold parameter to be fixed or to automatically adjust to optimize the CPU usage of the computer running the test. Since sending traffic and monitoring can be executed on different machines, you can also set the hostname or IP address of the machine that will do the monitoring, the monitoring types to use, and the communication ports to use.
  16. Select Next.
  17. On the Complete beSTORM wizard page, select Finish to start testing, or clear the Auto-start beSTORM scan now checkbox to exit the wizard and test later. Once you start the test, watch the status screen for periodic system notifications; beSTORM will open a dialog when a security vulnerability is found.


The beSTORM tool complies with the testing guidelines outlined in [ISASecure EDSA-310] ISCI Embedded Device Security Assurance – Common requirements for communication robustness testing of IP based protocol, as well as maintaining compliance for all ISASecure EDSA predefined project templates referred to as “modules”, with the following requirements:

[ISASecure EDSA-401] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of two common “Ethernet” protocols.
 
[ISASecure EDSA-402] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of the IETF ARP protocol over IPv4.
 
[ISASecure EDSA-403] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of the IETF IPv4 network protocol.


[ISASecure EDSA-404] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of the IETF ICMPv4 network protocol.

 

[ISASecure EDSA-405] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of the IETF UDP transport protocol over IPv4 or IPv6.

 

[ISASecure EDSA-406] ISA Security Compliance Institute Embedded Device Security Assurance – Testing the robustness of implementations of the IETF TCP transport protocol over IPv4 or IPv6.

 

Please refer to the ISASecure EDSA documentation for information relating to EDSA testing methodology, found at www.isasecure.org. The protocol features and versions under test are defined in the RFCs and other standard documents listed in the normative reference sections of the above EDSA specifications.