The service provider could use SYMACL or SYMAUTH settings on the array to restrict certain hosts/users.  SYMACL allows on certain hosts to access specified devices.  SYMAUTH restricts storage-related operations to specific users.  Both of these technologies are detailed in the Symmetrix Solutions Enabler CLI Array Controls Guide.  You can download it from [URL] or Powerlink.
EMC Community,  I've been doing EMC Symmetrix storage in some shape or fashion for the last 7 years, but I was asked a question today about gatekeepers about which I wasn't entirely sure of the answer so I thought I'd post it here and see what I get back. If you're aware of a document that discusses this aspect, please feel free to point me in the right direction.  My understanding is that a gatekeeper is generally a dedicated device of about 3-10 cylinders that can be used for SYMAPI/SYMCLI commands to a Symm. Although, really, any device (even a normal data lun) can be used as a gatekeeper to send commands to a Symm. If VMAX luns are being presented to a customer's server in a service provider environment, and that customer happens to know how all of this stuff works, what's to prevent them from installing SYMCLI on their "customer server" and sending commands to the VMAX, perhaps to provision their own storage without the knowledge of the storage administration team (AKA, free storage)?  If I remember correctly, there's not really an type of security on the host-side of a gatekeeper device and I'm not sure if there is on the array side or not either.  Can someone please provide a definitive answer on this?  Thanks!  -Jason
Gatekeeper Security - Service Provider