What will it do?
Quarantine will prevent all communications except those to the Tachyon server(s). This allows a Tachyon administrator to investigate and remove possible malicious software on the device.
Devices that have been quarantined will only be able to contact Tachyon. CRL checks must be set to soft. Certificate expiry can cause the Tachyon client to fail to connect to the switch. If a Tachyon client is no longer connected to Tachyon after quarantine, it will remain in quarantine. Please use with care, and please read this documentation carefully before use.
If the Tachyon Server has 1E Client installed (with Tachyon client features enabled) then it is possible to quarantine Tachyon Server like any other device. Therefore, please exercise caution before using this feature, and avoid targeting the server.
How do I quarantine a device?
You either need to load the 1E-Explorer-TachyonCore.zip file into Tachyon or download the quarantine product pack from the Tachyon Exchange and then define an Instruction set for the instructions. We recommend that you create an instruction set specifically for the quarantine instructions and permission this separately, for that you'll need to define a custom role and assign at least one management group to the role, for more details please refer to Tachyon Platform 5.2 - Instruction sets, Tachyon Exchange and custom roles - tutorial. The quarantine instructions are described in the following table:
|Are my devices quarantined? Warning: Please read the description before use.||This question returns a list of devices.|
|Quarantine selected devices. Warning: Please read the description before use.||This action quarantines all the devices in the scope of the action. Do not run this action without restricting the coverage to the devices you want to quarantine.|
|Release selected devices from quarantine. Warning: Please read the description before use.||This action releases all the devices in the scope of the action from quarantine.|
As you can see there is a warning attached to the name of each instruction. Quarantine is a powerful solution for use in extreme circumstances and should be used with care. We therefore recommend that Actioner permissions associated with the instruction set defined to contain the quarantine instructions should be assigned only to specific users. Users with Actioner permissions to use the quarantine instructions should also be warned that the instructions must be used carefully.
What do I need to know before I quarantine a device?
- Quarantine is available only on Windows, but not available on Windows XP.
- Quarantine requires that at least one switch URI and one background channel URI each resolve to IPv4 addresses.
- Quarantine will only work if a device's connection to the switch is over IPv4. This is because IPv6 is disabled by the quarantine mechanism.
- The CRLChecks setting in the 1E Client configuration file should be set to soft.
- As the device will be unable to contact anything but the tachyon server(s), the Tachyon client will be unable to retrieve CRLs for certificates requiring validation.
- CRLChecks can be set to hard, but this can cause the Tachyon client to lose connection to the switch when the CRL validity period is exceeded.
- Quarantine will persist until the Release selected devices from quarantine instruction is received.
- If a Tachyon client cannot be connect to the Tachyon Server, it will not be possible to issue this command.
- Any changes to the routing tables, IPv6 bindings or the hosts file made during quarantine will be reverted when the Release selected devices from quarantine instruction is received.
- If the persistent storage of the Tachyon client is deleted or modified by anything other than Tachyon whilst in quarantine, the Tachyon client will not be able to release the device from quarantine properly.
- Upgrading, uninstalling, installing or modifying the Tachyon client installation during quarantine is not supported. Do not upgrade, uninstall or install Tachyon, or issue an extensibility update whilst the Tachyon client is under quarantine.
- After a release from quarantine the IPv4 loopback address will not be resolvable. A restart is required to fix this.
- Quarantining a device will also stop it from being able to see Domain Controllers, so this may cause problems with logging on to the workstation. Cached logons should still work though.