2
2
0. MANUAL
3
3
------------------------------------------------------------------------------
4
4
5
- NSMnow Version 1.6.1
5
+ NSMnow Version 1.6.2
6
6
7
7
This MANUAL contains the command usage and details of the appropriate options
8
8
of the NSM Adminstration scripts.
9
9
10
10
If you have any questions or comments about the NSMnow scripts then please
11
11
direct them to the SecurixLive Team <
[email protected] >.
12
12
13
+ Contents:
14
+ 1. Copyright
15
+ 2. Description
16
+ 3. Command Usage
17
+ 4. Installation
18
+ 5. Troubleshooting
13
19
14
20
------------------------------------------------------------------------------
15
21
1. COPYRIGHT
@@ -38,14 +44,14 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
38
44
------------------------------------------------------------------------------
39
45
40
46
NSMnow is an open source tool to automate the installation and configuration
41
- of a Network Security Monitoring framework (NSM) built on sguil . Its primary
47
+ of a Network Security Montoring framework (NSM) built on Sguil . Its primary
42
48
use is to allow the user to deploy and build an NSM framework without the
43
- hassle of compiling, installing, and configuring all the tools separately .
49
+ hassle of compiling, installing, and configuring all the tools seperately .
44
50
45
51
NSMnow essentially has 2 modes of operation:
46
52
1. an interactive install, and
47
53
2. a non-interactive install.
48
-
54
+
49
55
In interactive mode you will be asked a series of questions throughout the
50
56
installation process giving you the option to skip or install that component.
51
57
@@ -67,7 +73,7 @@ Command line:
67
73
Usage: NSMnow [options]
68
74
69
75
Options:
70
- -c <file>
76
+ -c <file>
71
77
Defines an alternative configuration <file>. The default configuration
72
78
file that is used is NSMnow.conf which is located in the base
73
79
directory along with the NSMnow executable.
@@ -92,6 +98,8 @@ Options:
92
98
will also attempt to download system specific packages and libraries
93
99
using the native package management systems.
94
100
101
+ -V Show version information
102
+
95
103
-? Show this help
96
104
97
105
@@ -104,6 +112,9 @@ Long Options:
104
112
Explicitly define the packages that you want to perform the actions
105
113
on. Multiple directives are not currently supported.
106
114
115
+ --version
116
+ Same as -V
117
+
107
118
--help
108
119
Same as -?
109
120
@@ -116,11 +127,11 @@ Available packages:
116
127
server - All server specific components
117
128
client - All client specific components
118
129
119
- snort - Snort v2.8.4.1
130
+ snort - Snort v2.8.5
120
131
sguilclient - Sguil v0.7.0 (client components only)
121
132
sguilsensor - Sguil v0.7.0 (sensor components only)
122
133
sguilserver - Sguil v0.7.0 (server components only)
123
- barnyard2 - Barnyard v2.1.6
134
+ barnyard2 - Barnyard v2-1.7
124
135
sancp - Sancp v1.6.1-stable
125
136
sguiltools - Sguil tools: wireshark, p0f, tcpdump and tcpflow
126
137
@@ -130,21 +141,21 @@ Available packages:
130
141
------------------------------------------------------------------------------
131
142
132
143
To install a complete NSM all-in-one (i.e. sensor, server and client) solution
133
- then with root privileges , from the NSMnow directory, run:
144
+ then with root priveleges , from the NSMnow directory, run:
134
145
135
146
# ./NSMnow -i
136
147
137
- Alternatively you can choose to install the components separately using the
148
+ Alternatively you can choose to install the components seperately using the
138
149
the package keyword to explicitly define your packages. Multiple package
139
150
definitions are not currently supported.
140
151
141
- For example the following will install an NSM client:
152
+ For example the following will install an NSM client, with default options :
142
153
143
- # ./NSMnow -i --package=client
154
+ # ./NSMnow -i --package=client -y
144
155
145
- And for an NSM sensor only:
156
+ And for an NSM sensor only, with default options (ie no prompts) :
146
157
147
- # ./NSMnow -i --package=sensor
158
+ # ./NSMnow -i --package=sensor -y
148
159
149
160
150
161
When installing the packages NSMnow will determine if the source tarballs and
@@ -189,7 +200,7 @@ The sensor and server components can be stopped just as quickly with:
189
200
Read the provided MANUAL for options or run ./NSMnow -help
190
201
191
202
For detailed tips and guides on what NSMnow installs how the system is
192
- configured see the project page at http://www.securixlive.com/nsmnow/
203
+ configured see the project page at http://www.securixlive.com/nsmnow/
193
204
194
205
195
206
------------------------------------------------------------------------------
@@ -219,7 +230,7 @@ to the log file. This ensures that everything is captured when troubleshooting.
219
230
This also may appear that nothing is happening. However, you are able to get a
220
231
full picture of what is going on by tailing the log file. We do this
221
232
extensively during testing to get the full picture of what is happening.
222
-
233
+
223
234
# tail -f ./NSMnow.log
224
235
225
236
@@ -267,3 +278,4 @@ update the rules. I will first update the rules on the sensor under that will
267
278
exist at "/etc/nsm/thor/rules" and ensure the corresponding *.map files are also
268
279
updated at "/etc/nsm/thor". Secondly I'll ensure the same rules are updated on
269
280
the server under the "/nsm/server_data/athena/rules/thor".
281
+
0 commit comments