Thanks for info!
I was thinking the same way just wanted to make sure i was on track. The other reason for this is that i may be able to propse it as an alternative to a client requiring IPSEC system we use that is clunky at best and also controlled by a 3rd party...something i am not very keen on..
My main concern was that i have to make sure it fullfills standards set by government and other parties that, dare i say it, take so long to ratifiy anything it is out of date by the time we are allowed to use it to keep our accrediation for the connection. So if i can make this secure then i may be able to propose it as an alternative it i can get the right people to say it is ok.
Although not mentioned within work i can forsee a need for peole to be able to access allowed applications and the like from anywhere at anytime in case of a policy change or emergency.
I was looking to beef up the security of not only the connection but also that data passed through it using the Cisco Secure Desktop, something i have been playing around with in my 'spare time' at work. This would mean that any data used by the connections and downloaded data is removed on log out. I was then thinking about using radius/token based authentication for ths and then take them straight to the citrix log on page.
The main problem i have is the confidentiality/protective marking of the data...bane of my life..but this may overcome any problems with that aside from shoulder surfers.
See how it goes anyway....during the pilot, knowing my luck, they might say that it is not worth it. This would be a shame as i can see so much potential for it just finding it hard to put it across without mentioning the access from anywhere, which i have been 'told' should be kept quite unless asked for.....


Something about not making more work for ourselves and some other not very good reasons. However i will keep trying to break them down from within..should be in place before they even know what is happening...
