SVS layer piracy
Submitted by AxeMan on 21 May, 2008 - 17:25.
Hi
I am defining the standards for a 12000+ user site. We are planning to go 100% SVS.
One area of concern is piracy. E.g. anyone accessing the VSA repository can potentially copy them to a USB drive and use them anywhere - as with normal corporate MSIs, packages are "cracked" and therefore easily distributed.
In this scenario access to the source directory can at least be controlled.
But unique to SVS is the ability for a support person with Admin rights to go to ANY PC and export a layer to a USB stick - thus the complete source is available.
Has anyone come up with a way of preventing this? e.g. layer change state scripts with password? or is there a standard tool which can provide added security to a layer.
Thanks! George
SVS layer piracy
George,
You definetly have a point. And there is not a real good answer.
The only best thing you can do is to make sure the repository is save with rights.
It does not prevent the admins from copying layers.
You could build in a vbs script that verifies the domain the pc is in, but that script is also easy to delete inside a layer.
Regards
Erik
www.dvs4sbc.nl
key to do export / import of the layers
It will be a good idea to implement some kind of password / key to do export / import of the layers. Ideal will be some 4 layer (level) security some thing like, the base key can only view, the 2nd one can import new and create new layer, the 3rd one can export and delete & the final one has the super sights to do what ever he wants. I have seen similar feature in industrial automation products such as HMI (Human Machine Interface), and in the PLC/DCS configuration tools.
But I don’t know how much of time, the development team is going to spend on this little feature request.
Regards,
Swami.
You could, using the SDK,
You could, using the SDK, write your own tools to replace SVScmd (really simple to do) and even admin if you want that would require a password or what not and then remove the original SVS tools.
This isn't 100% secure because the driver and library don't have the concept of passwords and such so anyone that brings their own copy of SVSadmin could just as easily export--but at least it would require them to go through the effort of doing so and your average worker probably isn't going to know about svs anyway so they wouldn't know they could do that.
SVS 3?
I heard that there was going to be more security built into SVS 3. Can anyone confirm this?
Depends on what you mean by
Depends on what you mean by security?
Are we writing more secure code and doing better threat modeling? yes.
anything else would just be speculation as we haven't officially announced any of 3.0s new features.