Control Compliance Suite

 View Only
  • 1.  8.6 Policy Module

    Posted Feb 26, 2009 07:22 PM
    Does everyone the needs to be involved in the life cycle of a policy (initiator, reviewer, etc) need to have access to the console? Or is this possible through the policy portal?
    Message Edited by nova924 on 02-26-2009 04:22 PM


  • 2.  RE: 8.6 Policy Module

    Posted Feb 26, 2009 07:34 PM

    PM is not my area of expertise, but I do know that you can grant a very limited access to CCS via its roles (aka Segregation) system.  You can then allow certain users to run the console (they can just run it off your CCS App Server's \BVSMC share, and it will self-install) and they will only see UI for the features you've chosen.

     

    The roles are configured in System | Roles, and there is a 'Policy Reviewer' role that may suit your needs perfectly.

     

    KDH



  • 3.  RE: 8.6 Policy Module

    Posted Feb 26, 2009 08:16 PM

    I was hoping not to have to grant access to the console. :( But if that is the only way, then so be it.  I was hoping that I could assign the policy roles and have the reviewers log into the policy web portal to review and comment. Much like the policy audience does.

     

    The issue is the there is the potential to have a "large" amount of people that should review various policies. Thus the access to the CCS app server would expand.



  • 4.  RE: 8.6 Policy Module

    Posted Feb 26, 2009 09:51 PM

    Alas, this is the limit of my PM knowledge; I deal with the CCS and RMS cores, and PM is a border country. :)  If no PM folks chime in on this thread, then give tech-support a call, they may have some better ideas.

     

    KDH

     



  • 5.  RE: 8.6 Policy Module

    Posted May 26, 2009 06:10 AM

    we also have done this practice previously



  • 6.  RE: 8.6 Policy Module

    Posted May 26, 2009 06:11 AM
    hi nova
    please let me know whether problem is resolved; so that we can implement same solution if we faced this type of problem somewhere