My bad. I could've sworn that I mentioned that I'm looking at fewer than 100 users.
The 'rules' bit refers to the notion that users within the physical premise should not have to use the two-factor auth mechanism. In other words, when I'm outside the firewall I need a hardware key of some sort - when I'm in the office my password is sufficient. I appreciate whatever input is available. RS On Wed, Jul 29, 2009 at 11:11 PM, Dean Cunningham<[email protected]> wrote: > Size of organisation? > what sort of rules "dependent on physical location" can you give some > examples? > > On Thu, Jul 30, 2009 at 2:45 PM, Richard Stovall <[email protected]> wrote: >> >> I'm throwing this out into the ether 'cause I really don't know where to >> start. >> >> I'm looking for strong remote access / user authentication for a >> Windows 2003 functional level domain. >> >> RSA SecureID >> -or- >> Aladdin SafeWord >> -or- >> Entrust IdentityGuard >> -or- >> Authenex-ASAS >> -or- >> Quest Defender >> -or- >> something else? >> >> Desired features are: >> >> 1) minimal cost (naturally) >> 2) minimal installation footprint >> 3) flexibility (different rules depending on where the user is >> physically located) >> 4) ease of management >> 5) upgrade-ready (to future AD versions, etc.) >> >> All thoughts and experiences are welcome. >> >> Thanks, >> RS >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
