Managing the Archer Environment
We have recently implemented a few of the Archer solutions, but there are several organizations throughout the company who are itching to evaluate/implement additional solutions. As we are new to this suite we are looking into how to best manage the environment:
What is a good organizational structure for
- evalutaing/onboarding new solution requests?
- Configuring new solutions?
- Maintaining existing solutions?
At last summer's Summit I attended a presentation called "7 Habits of Highly Effective GRC Environments" (or something similar to that title) and have found it to be extremely useful. I"m wondering if anyone else has implemented a support model similiar to that and how it has worked. Or, has anyone done anything differently that they'd be willing to share?
Looking for any suggestions you may have.
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
If you haven't already I would recommend registering for access to the private RSA communities as follows. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.
Once you complete the registration, you will then be able to relocate this post (select "Move" under "ACTIONS" along the right) and also directly submit any new questions. It will then have more visibility by fellow end-users, EMC employees, and partners that are eager to assist.
I'm also including the community manager who can assist in making sure you get the best experience possible.
Thank you for the reply. Actually i am already registered, and in fact was in the community when i posted my question. Obviously i did something incorrectly. Any suggestions on where i should move my question to in order to get it to the most appropriate crowd?