i am pondering a technical IT config management best-practices problem. I'll put it behind the cut because a lot of you really don't care.
so, i've got a bunch of network devices. some of them are reachable via ssh, and some by telnet. all of them are reachable on their console by telnetting to a console server.
the devices, and the console server, all authenticate via RSA's securid two factor authentication.
most of my network devices let me send a magic SNMP string that tell the devices "hey, tftp your config over here".
but some of them don't. those are the troublesome ones.
the easiest way is for me to set up a static password that's good for half an hour or so per day, and run my "login and grab the config" scripts with those. except for the fact that it would be allowing something with a static password to log into my network gear. even time-restricted, that's more of a big flapping hole than i'm comfortable with.
what are other people doing for config management on network devices that don't support (either by design or by "to be fixed in a later version of code" bugs) snmp-triggered tftp?
EDIT: the problem i am trying to solve is how to get automated periodic downloads of configs from these machines, when i can't authenticate with securid tokens (since that requires a human) and static passwords are pretty much too insecure.
this is the sort of thing that doesn't seem to make it into the "best practices" docs i've found so far, but i'll likely continue pouring over docs today...
thoughts? suggestions?
so, i've got a bunch of network devices. some of them are reachable via ssh, and some by telnet. all of them are reachable on their console by telnetting to a console server.
the devices, and the console server, all authenticate via RSA's securid two factor authentication.
most of my network devices let me send a magic SNMP string that tell the devices "hey, tftp your config over here".
but some of them don't. those are the troublesome ones.
the easiest way is for me to set up a static password that's good for half an hour or so per day, and run my "login and grab the config" scripts with those. except for the fact that it would be allowing something with a static password to log into my network gear. even time-restricted, that's more of a big flapping hole than i'm comfortable with.
what are other people doing for config management on network devices that don't support (either by design or by "to be fixed in a later version of code" bugs) snmp-triggered tftp?
EDIT: the problem i am trying to solve is how to get automated periodic downloads of configs from these machines, when i can't authenticate with securid tokens (since that requires a human) and static passwords are pretty much too insecure.
this is the sort of thing that doesn't seem to make it into the "best practices" docs i've found so far, but i'll likely continue pouring over docs today...
thoughts? suggestions?
no subject
Date: 2005-07-28 03:54 pm (UTC)to get to the consoles, i have to go over the network to my console server and authenticate.
the problem is authenticating in a way that doesn't make the auditors hit me with a rolled up newspaper, but that still lets me use an automated login (which usually means a static password).
the network devices can speak tacacs and/or securid. or static password. i suppose they could do radius, but that doesn't do much more for me.
ponder ponder ponder.
no subject
Date: 2005-07-28 04:11 pm (UTC)Out of band. Works neat.
CZ
no subject
Date: 2005-07-28 04:15 pm (UTC)no subject
Date: 2005-07-29 03:58 am (UTC)no subject
Date: 2005-07-29 12:32 pm (UTC)no subject
Date: 2005-07-29 05:39 pm (UTC)You want to run an automated script that will then write over an existing file (albeit a system file) on a number of computers who are the same network on a regular basis to ensure everyone is on the same page?
no subject
Date: 2005-07-29 05:41 pm (UTC)no subject
Date: 2005-07-29 05:47 pm (UTC)if there's a static password account, i have a script that logs in, says "gimme your config" and then logs out. but a static password account is a big honking security hole.
hence, my dilemma.
no subject
Date: 2005-07-29 05:52 pm (UTC)I should probably ask you in person some time how SysID works. I am rather fascinated by it.
no subject
Date: 2005-07-29 06:00 pm (UTC)I should probably ask you in person some time how SysID works.
there's a secret number that exists on both your keyfob and on the securid server. every minute, it generates a new number based on that secret number and the current time. so the server knows what number you should have every minute and it can say with some confidence that you have the physical token with you ("something you have"). the PIN that you type in with that is the "something you know" that proves it's you holding the token fob.
"two factor authentication" generally means "something you have" plus "something you know".
another example is your ATM card and the PIN.
no subject
Date: 2005-07-29 06:53 pm (UTC)Ok, so back to the problem at hand...you need a secure method to copy the config file to be stored on another machine in the same network. The roadblock is authentication, which is what is needed for it to pass the file outward and check in on the other machine. The problem doesn't lie on the individual machines themselves, necessarily, it's on whichever machine you end up storing the data - assuming a push technology instead of a pull.
TACACS+ to the rescue
Date: 2005-07-29 05:17 am (UTC)You should be able to use TACACS+ to set up a password account in your TACACS server which is restricted to just running the commands to do a show running and/or to FTP a configuration copy off the Cisco.
This is the "Authorization" feature of TACACS+, not supported with RADIUS. If you have a separate TACACS server (e.g. CiscoSecure ACS) that forwards to SecurID, you can hardcode this restricted passworded account in TACACS, and the request will never make it up to ACE/Server.
Kevin Kadow
Re: TACACS+ to the rescue
Date: 2005-07-29 12:31 pm (UTC)thanks!
no subject
Date: 2005-07-30 12:53 am (UTC)time I had a setup like this, I did like CZ and just spoonfed them the passwords over dedicated
serial links and then they slurped up their configs over the network.