Export "Registry Vulnerabilities" scan to another computer?
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login | |
|
Export "Registry Vulnerabilities" scan to ano... - 20.Sep.2005 7:35:00 AM
|
|
|
wurtter
Posts: 11
Joined: 23.Mar.2005
Status: offline
|
I have created several custom "Registry Vulnerabilities" to scan for on my PC and I would like to send them to a colleague in a different site for him to use on his LANguard NSS. I do not see a way to export them. Is there a way? I would hate for him to have to type them all in manually.
Thanks, /*Raj*/
|
|
|
|
RE: Export "Registry Vulnerabilities" scan to... - 22.Sep.2005 5:11:00 AM
|
|
|
Nicks
Posts: 2769
Joined: 17.Mar.2003
Status: offline
|
Hi,
The vulnerabilities are stored in the database which stores the scanning proifles, which is called operationsprofiles.mdb, and stored in <GFI\LANguard Network Security Scanner\data>. Note that this will store all the scanning profiles.
You can also export/import particular profiles using the impex.exe command line utility which is found in the main LANguard NSS directory. Use impex.exe for usage information.
|
|
|
|
RE: Export "Registry Vulnerabilities" scan to... - 22.Sep.2005 5:13:00 AM
|
|
|
Nicks
Posts: 2769
Joined: 17.Mar.2003
Status: offline
|
Note that the user that gets the operationalprofiles.mdb will loose his customizations (if any) on the scanning profiles.
If the you want to import the new vulnerabilities, but on the other hand keep your customizations you can use:
- impex.exe command line tool which was mentioned in my previous post
or
- update.exe with the following parameters: Export vulnerabilities: update /n vulns.xml Import vulnerabilities: update /n /i /x vulns.xml [ September 22, 2005, 11:14 AM: Message edited by: nicks ]
|
|
|
|
RE: Export "Registry Vulnerabilities" scan to... - 22.Sep.2005 10:40:00 AM
|
|
|
wurtter
Posts: 11
Joined: 23.Mar.2005
Status: offline
|
I called the GFI tech support and was a bit disapointed... the tech didn't even know what the "impex" tool was.
The command/program is not that well documented and does not explain all of the options. So I did a full export to get the data I was looking for and finally got what I needed. Here is an example of how to export just one of the checks from the source computer:
code:
impex /f:regcheck.xml /ae:"Blaster Worm" /at:"Registry Vulnerabilities" /d
Broken down...
1) /f:regcheck.xml - XML file name to safe the data too. 2) /ae:"Blaster Worm" - Name of the rule 3) /at:"Registry Vulnerabilities" - Alert type name 4) /d - Update the XML file
On the destination computer you would run this command:
code:
impex /f:regcheck.xml /i
Hope this helps.
/*Raj*/
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|