IMPORT POLICIES FOR DLP 10.5
Created: 16 Nov 2012 | Updated: 11 Dec 2012 | 9 comments
This issue has been solved. See solution.
Hi,
SOMEBODY KNOWS HOW I CAN IMPORT POLICIES FOR VONTU DLP 10.5. I FOUND THIS PATH: /opt/Vontu/Protect/config/templates BUT DON´T WORKS. I HAVE COPIED THE FILE ON THIS PATH AND WHEN I TRY TO GET THE FILES DON'T APPEARS.
Thanks in advance
Discussion Filed Under:
Comments 9 Comments • Jump to latest comment
Moved to DLP forum
SEP Knowledge Base
Endpoint SWAT
This is the first step you import the policy: copy the xml file to the location /opt/Vontu/Protect/config/templates
Then, you need to log into the DLP Enforce Console, choose to add a policy, and select add from template. At the end of the templates list, you will find out your policy name that you copyed to /opt/Vontu/Protect/config/templates.
hello yang_zhang,
I've been copied the file as you as mentioned, but don't works and i don't know what do do.
regards.
hello raul,
Does your source and destination are at the same DLP version ? If not it will be a little bit more tricky to import them.
If they are, so once you have copied xml templates to the directory you mentionned you can use them when you create a new policy (from a template) but not directly as policy. some kind of rules cannot be exported so be sure this is the right way to proceed if you want to copy policy from one solution to another.
regards.
hello stephane,
In fact the source and destination have the version 10.5. And as you as mentioned i have copied and import them to the right path, i think so, but don´t works. Its possible that error is in the file rights? when i copy the file to the destination.
thanks
Hi Rahul,
Please refer below links and detailded steps
https://www-secure.symantec.com/connect/forums/how...
https://www-secure.symantec.com/connect/forums/dlp...
- check that xml template are readable by protect user on your enforce server.
- you can also try to restart "Vontu Manager" service. It should not be necessary but it can solve some issue sometimes when everything seems to be crazy.
- did you export this template from the same OS system. If you tranfer them from linux to windows (or win to linux) you can have some file format issue. in this case, you can perform a dos2unix or unix2dos in your unix environnement.
so if it still doesnt work and if it allowed you can share the template with us (or privately with me) and i can check file content/format/.....
Sthepane,
hi, how are you. Sorry for write until now, only i want to tell you that export policies works. The solution as you mentioned is:
first, that the file template are readable by protect, in my case was root and i had it to changed
and second the file xml was conteined one special character (á) can you belive it. I think this one was the even worse error.
thanks for you help.
best regards
Hi Rahul,
Exporting A Policy as a Template
Your template is served
Importing a Template as a Policy.
If the policy in the template does not have any EDM/IDM/DGM conditions, you will now have a new policy.
If the policy in the template has EDM/DGM conditions, you will be asked for a Database index during import. You can choose to not provide any Database index, in which case the corresponding conditions will be dropped from the created policy
If the policy in the template has IDM conditions, you will be asked for a Document index during the import. Again, you can choose no index and drop the conditions.
If the policy being imported has both EDM/DGM AND IDM conditions, you will be issued a warning and the IDM conditions will be dropped.
Would you like to reply?
Login or Register to post your comment.