Webinar Announcement: 'Are You Checking the Device State When Granting Remote Access?'
Absolute Software and others are hosting a webinar on remote access security based on device status. It will explain the risks of uniform access permission and the importance of dynamic control according to device health.
📋 Article Processing Timeline
- 📰 Published: April 22, 2026 at 18:00
- 🔍 Collected: April 23, 2026 at 00:02 (6h 2m after Published)
- 🤖 AI Analyzed: April 23, 2026 at 07:42 (7h 39m after Collected)
Details and Registration here
■ Remote access cannot be protected just by "who uses it"
While the development of remote access environments has progressed, it is not uncommon for access control decisions to be based primarily on "user authentication," without sufficient consideration for the state of the connecting device. In reality, risks vary greatly depending on the state of each device, such as the operational status of antivirus software, the presence or absence of encryption, OS versions, and location information. Even if the user is a legitimate employee, if there are deficiencies on the device side, there is room to review the operation of uniformly granting connection to that device.
■ Connection permissions that ignore device state lead to oversights
In many companies, the decision of whether to grant a connection is fixed, and they have not yet achieved operations that change the connection destination or available scope according to the conformity status of the device. Therefore, a device whose antivirus has been disabled, a device without encryption, or a device being used from an unexpected location may be granted connection under the same conditions. When device management and access control are separated, the challenge is that even if an anomaly is detected, it cannot be reflected in the connection rules, resulting in delayed responses.
■ Changing connection rules according to the device's conformity status
In this seminar, we will explain the concept of determining conformity or non-conformity based on the device's state, such as antivirus, encryption, location information, and OS version, by combining Absolute Secure Endpoint and Absolute Secure Access, and controlling access permissions and connection destinations according to the results. For example, by permitting connections to business systems only for devices that meet the conditions, and limiting the connection destinations for devices that do not meet certain conditions, it is possible to respond to risks that are difficult to prevent with uniform permission. We will introduce how to realize remote access operations that are more in line with the actual situation by linking the visualization of device states with access control.
■ Organizer/Co-sponsor
Absolute Software
■ Cooperation
Open Source Katsuyo Kenkyujo
Majisemi
Details and Registration here
Majisemi will continue to hold webinars that are "useful to participants."
Public materials from past seminars and other seminars currently recruiting participants can be found ▶here.
Majisemi
3F Shiodome Building, 1-2-20 Kaigan, Minato-ku, Tokyo 105-0022
Contact: https://majisemi.com/service/contact/
■ Remote access cannot be protected just by "who uses it"
While the development of remote access environments has progressed, it is not uncommon for access control decisions to be based primarily on "user authentication," without sufficient consideration for the state of the connecting device. In reality, risks vary greatly depending on the state of each device, such as the operational status of antivirus software, the presence or absence of encryption, OS versions, and location information. Even if the user is a legitimate employee, if there are deficiencies on the device side, there is room to review the operation of uniformly granting connection to that device.
■ Connection permissions that ignore device state lead to oversights
In many companies, the decision of whether to grant a connection is fixed, and they have not yet achieved operations that change the connection destination or available scope according to the conformity status of the device. Therefore, a device whose antivirus has been disabled, a device without encryption, or a device being used from an unexpected location may be granted connection under the same conditions. When device management and access control are separated, the challenge is that even if an anomaly is detected, it cannot be reflected in the connection rules, resulting in delayed responses.
■ Changing connection rules according to the device's conformity status
In this seminar, we will explain the concept of determining conformity or non-conformity based on the device's state, such as antivirus, encryption, location information, and OS version, by combining Absolute Secure Endpoint and Absolute Secure Access, and controlling access permissions and connection destinations according to the results. For example, by permitting connections to business systems only for devices that meet the conditions, and limiting the connection destinations for devices that do not meet certain conditions, it is possible to respond to risks that are difficult to prevent with uniform permission. We will introduce how to realize remote access operations that are more in line with the actual situation by linking the visualization of device states with access control.
■ Organizer/Co-sponsor
Absolute Software
■ Cooperation
Open Source Katsuyo Kenkyujo
Majisemi
Details and Registration here
Majisemi will continue to hold webinars that are "useful to participants."
Public materials from past seminars and other seminars currently recruiting participants can be found ▶here.
Majisemi
3F Shiodome Building, 1-2-20 Kaigan, Minato-ku, Tokyo 105-0022
Contact: https://majisemi.com/service/contact/