
VMware, Inc. 81
14
vShieldEndpointdeliversanintrospection‐basedantivirussolution.vShieldEndpointusesthehypervisorto
scanguestvirtualmachinesfromtheoutsidewithoutabulkyagent.vShieldEndpointisefficientinavoiding
resourcebottleneckswhileoptimizingmemoryuse.
vShieldEndpointhealthstatusisconveyedbyusingalarmsthatshowinredand
yellowonthevCenterServer
console.Inaddition,morestatusinformationcanbegatheredbylookingattheeventlogs.
Thischapterincludesthefollowingtopics:
“ViewvShieldEndpointStatus”onpage 81
“A l a r m s ” onpage 82
“Events”onpage 83
“A u d i t Messages”onpage 86
View vShield Endpoint Status
MonitoringavShieldEndpointinstanceinvolvescheckingforstatuscomingfromthevShieldEndpoint
components:thesecurityvirtualmachine(SVM),theESXhost‐residentvShieldEndpointmodule,andthe
protectedvirtualmachine‐residentthinagent.
To view vShield Endpoint status
1InthevSphereClient,gotoInventory>HostsandClusters.
2 Selectadatacenter,cluster,
orESXhostresourcefromtheresourcetree.
3ClickthevShieldApptab(orvShieldtabonESXhosts).
4ClickEndpointStatus.
vShield Endpoint Events and Alarms
14
IMPORTANTYourvCenterServermustbecorrectlyconfiguredforvShieldEndpointsecurity:
NotallguestoperatingsystemsaresupportedbyvShieldEndpoint.Virtualmachineswithnon‐supported
operatingsystemsarenotprotectedbythesecuritysolution.
Allvirtualmachines(withsupportedoperatingsystems)thatresideonavShieldEndpoint‐protectedESX
hostmustbeprotectedbyavShieldEndpointmodule.
NotallESXhostsinavCenterServermustbeprotectedbythesecuritysolution,buteachprotectedESX
musthaveanSVMinstalledonit.
CAUTIONvMotionmigrationofaprotectedvirtualmachineareblockedifthetargetESXisnotenabled
forvShieldEndpoint.MakesurethattheresourcepoolforvMotionofprotectedvirtualmachines
containsonlysecurityenabledESXhosts.
Commenti su questo manuale