EU Radio Frequency Directive (RED) Cybersecurity Instruction Reference Guide

Technical Documentation>  TZ Series with Internal Wireless>  Access Port Changes>  API Access
Table of Contents

API Access

Use these steps only if applicable to your environment.

SonicWall supports multiple API login methods. For interoperability and backward compatibility with systems, SonicWall includes support for older cryptographic suites and certificate sizes. Below are mechanisms for users to access the SonicWall API:

  • RFC-7616 HTTP Digest Access authentication is recommended for Radio Equipment Directive compliance.

    • RFC-7616 HTTP Digest Access authentication is the default web interface authentication method. It is also enabled by default for API authentication.
    • RFC-7616 HTTP Digest Access authentication supports SHA256 and MD5 digest algorithms/hash mechanisms. SHA256 is the default, but using MD5 is not recommended, causing you to not be compliant with the directive.
  • RFC-2617 HTTP Basic Access authentication is not recommended and is disabled by default. You will not be compliant using this authentication.
  • CHAP authentication is not recommended and is disabled by default, and you will not be compliant if you use CHAP.
  • Public Key authentication is recommended with a RSA modulus of 2048 bits and above. Using an RSA modulus of 1024 bits is not recommended and will cause you to not be compliant. This disabled by default.
Chat