日本語 
H.C. Networks Corporation, announces launches of “Account@Adapter+ V7 Version 7.03,” an authentication, account management, certificate issuance, and DHCP appliance developed and sold in-house, which adds new functions to strengthen security and keep up with the constantly changing external environment.
Background
As a result of pandemic countermeasures and progress in work style reforms, cloud utilization and remote work have accelerated, and wireless LAN environments that allow network access from anywhere within the company have been established with the aim of improving work mobility and streamlining meetings. As a result, there is an even greater need for stronger security for network access.
In recent years, the external environment surrounding authentication has undergone major changes, such as voluntary organizations shortening the validity period of certificates and Microsoft and Google discontinuing SMTP AUTH. Furthermore, requirements such as iPSK support and proper certificate key usage have also become necessary.
In response to this background, “Account@Adapter+ V7” has been enhanced with functionalities aimed at achieving safer and more efficient authentication operations than ever before.
Also Read: Asuene Partners with ERM to Strengthen SSBJ, CSRD Services
Main new features of Account@Adapter+ V7.03
Automatic management of TLS server certificates with ACME protocol support
The voluntary organization CA/Browser Forum (Certification Authority Browser Forum) has drawn up a schedule to shorten the maximum validity period for TLS server certificates to 200 days from March 2026, 100 days from March 2027, and 47 days from March 2029, in order to strengthen security. As a result, the frequency of certificate renewals will increase, increasing operational burdens, and automated certificate management is becoming necessary.
This version supports the ACME protocol, which enables automatic acquisition and renewal of TLS server certificates, automates certificate lifecycle management, significantly reducing the burden on administrators and preventing risks such as service outages due to expiration.
Supports OAuth 2.0 authentication for safer email integration
While Microsoft and Google plan to phase out SMTP AUTH, this version supports OAuth 2.0 authentication for the email sending function. This allows you to safely use cloud email services such as Microsoft 365 and Google Workspace, and allows for continuous operation without relying on the traditional SMTP AUTH. It also eliminates the need to store and manage IDs and passwords for the email sending function, reducing the burden on administrators and the risk of information leaks.
iPSK support enhances wireless LAN security and improves operational efficiency
With the conventional common PSK method, multiple devices share a single key for the SSID, meaning that if the key is leaked or used fraudulently, the impact is widespread. With iPSK, a different PSK can be assigned to each device or user, so in the unlikely event of a leak or fraud, the impact can be localized and keys can be changed individually, achieving both security and operability.
In light of this, this version implements support for iPSK. This allows individual PSKs to be distributed and authenticated for each MAC address, reducing the risks associated with shared key operations and supporting flexible wireless LAN authentication.
Automatic assignment of KeyUsage ensures the reliability and compatibility of certificates
As the reliability and suitability of certificates become more important than ever, it is becoming increasingly important to properly assign a KeyUsage extension to server certificates. In particular, if a certificate does not meet the official TLS server certificate requirements set by Apple in iOS 13 or later, it may not be trusted and connections may not be possible.
This version implements a function to assign the appropriate KeyUsage attribute when issuing a TLS server certificate. Specifically, the required KeyUsage, such as “Digital Signature” or “Key Encipherment,” is automatically assigned depending on the certificate’s intended use.
SOURCE: PRTimes
English