VM

 View Only

  • 1.  VMSECURE won't HOLD IDENTITIES

    Posted Jul 14, 2023 11:36 AM

    Discussion point:

    Should VMSECURE hold an IDENTITY? If VMSECURE knows it's not in an SSI environment, then IDENTITY and USER are effectively synonymous, so why treat them differently?

    Background/Use Case:

    By design, an IDENTITY (vs USER) in a file for VMSECURE MULTIPLE HOLD is not held. 

    We have a process that holds dormant users... it doesn't distinguish between a USER and an IDENTITY. (dormant is an id that has not been logged onto, autologged nor one of its disks linked to in n days)

    Ids that are in hold status for x days are then deleted. This provides a nice grace period during which it's trivial to reinstate if needed.



  • 2.  RE: VMSECURE won't HOLD IDENTITIES

    Broadcom Employee
    Posted Jul 17, 2023 09:18 AM

    Don, thanks for sharing this idea.  I have copied it to Ideation and opened it for voting to the community.   You can find the Ideation Home Page here: https://community.broadcom.com/participate/ideation-home

    Those interested in this Idea can vote for it at the following link:  https://community.broadcom.com/idea/vmsecure-wont-hold-identities

    Voting for specific Ideas under the "VM" Category on the Ideation page allows the Broadcom VM team to prioritize which Ideas to prioritize for research.


    Original Message