Many units deploy web access certification systems, focusing on identification, while ignoring another important element of access control.——The identification answer is"Who are you?"The terminal compliance answer is"Is your equipment secure enough to get in?"A terminal that is infected with a virus and has not been patched for long, even if the identity certificate passes, it can be a safe break to the inner web. This article shows how the end-compliance check works and where it is located in the network access certification system.
What exactly is the compliance check?
The core of terminal compliance checks is confirmed access to the network terminals"Health status"The usual checks include whether the anti-virus software is installed and running, whether the virus library is updated in a timely manner, whether the operating system patches are complete, whether the system firewalls are open, whether prohibited software is installed, or if there is no safety component to install.
Checking timing: mandatory before network entry, running review
Terminal compliance checks generally take two timings: one single check before the end, without attaining the target, and the other cyclical review in operation, because the safety status of the end is changing, possibly reaching the target today, or with the virus tomorrow or with the patch expired. The network access certification system can be combined with NATSHEL_SEAMLESS_AUTH and cycle strategy, periodical reviews of the net terminal, tactically guided repair, isolation or alert if an anomaly is detected. One pre-net inspection is not enough; the dynamic state of the end must be continuously reviewed to get its bottom.
What about the non-achieving terminal?
The end failure process directly determines the employee's acceptance of the system. A common practice is to level it up: automatically direct or force a repair after networking on an issue that can be repaired automatically (e.g., poison-killing not running, patches expired); to provide clear guidelines for fixing which needs manual treatment, rather than simply refusing access to the Internet; and to impose isolation on restricted networks for high safety risk terminals (e.g. malicious processes detected), the purpose of processing is to block access to the inner network."I'm gonna fix it. I'm gonna get a lot of risk to keep me in quarantine."Instead of being completely closed to all substandard terminals, it would affect the normal course of business.
Method of checking: How to choose the Agent probe and no proxy scan
The end-compliance check is achieved in two main ways: by installing the Agent probe at the terminal, actively collecting and reporting safety status, full and real time information but requiring a customer at the end; and by deploying simple but limited information available through passive non-agent (e.g. switchboard and protocol-based) checks. Enterprises usually use it according to a scenario combination: staff office terminals are equipped with Agent for depth checks, visitors and outside equipment for light weight checks or no inspections.
Attention to compliance inspections
The end compliance check is to be conducted with regard to a number of points when it lands: first, the inspection requires exemptions and exceptions that do not cause injury to key operational terminals by error in its strategy; second, the results are to audit traces for retroactive and compliance review; third, inspections cannot over-invade personal equipment, especially as concerns BYOD equipment, so that privacy disputes are avoided; fourth, the inspection strategy needs an emergency response plan and, if the services are abnormal, does not result in a complete network terminal being unconnected. Compliance checks are access control plus sub-items that significantly improves inner safety levels and instead become a transportation burden.
The end-of-end compliance check in the network access certification system is essentially a process of"Trusted identity."Upgrade To"I.D.+ Terminal Double Trust". The final compliance check is required to maintain the security bottom without compromising normal operations.