зеркало из https://github.com/mozilla/MozDef.git
add conf file docs, closes #276
This commit is contained in:
Родитель
f3f6edefa4
Коммит
8c3fe857fe
|
@ -5,11 +5,11 @@ Using local accounts
|
|||
--------------------
|
||||
|
||||
MozDef ships with support for persona which is Mozilla's open source, browser-based authentication system. You should be
|
||||
to use any gmail or yahoo account to login to get started.
|
||||
to use any gmail or yahoo account to login to get started.
|
||||
|
||||
To change authentication to something less public like local accounts here are the steps:
|
||||
To change authentication to something less public like local accounts here are the steps:
|
||||
|
||||
Assuming Meteor 9.1 (current as of this writing) which uses it's own package manager:
|
||||
Assuming Meteor 9.1 (current as of this writing) which uses it's own package manager:
|
||||
|
||||
1) From the mozdef meteor directory run '$ meteor remove mrt:accounts-persona'
|
||||
2) 'meteor add accounts-password'
|
||||
|
@ -17,3 +17,63 @@ Assuming Meteor 9.1 (current as of this writing) which uses it's own package man
|
|||
4) Restart Meteor
|
||||
|
||||
This will allow people to create accounts using almost any combination of username/password. To add restrictions, limit domains, etc please see: http://docs.meteor.com/#accounts_api
|
||||
|
||||
Conf files
|
||||
----------
|
||||
MozDef python scripts in almost all cases expect to be given a -c path/to/file.conf command line option to specify configuration/run time options.
|
||||
|
||||
These files all follow the same format:
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
setting1=value1
|
||||
setting2=value2
|
||||
|
||||
|
||||
All programs do their best to set reasonable, sane defaults and most will run fine without a conf file. By default programname.py will look for programname.conf as it's configuration file so if you follow that convention you don't even need to specify the -c path/to/file.conf option.
|
||||
|
||||
Special Config Items
|
||||
+++++++++++++++++++++
|
||||
|
||||
Here are some tips for some key settings:
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
esservers=http://server1:9200,http://server2:9200,http://server3:9200
|
||||
|
||||
is how you can specify servers in your elastic search cluster.
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
defaulttimezone=US/Pacific
|
||||
|
||||
is how you set the default timezone to something other than UTC
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
backup_indices = intelligence,kibana-int,alerts,events,complianceitems,.jsp,.marvel-kibana,vulnerabilities
|
||||
backup_dobackup = 1,1,1,1,1,1,1,1
|
||||
backup_rotation = none,none,monthly,daily,none,none,none,none
|
||||
backup_pruning = 0,0,0,20,0,0,0,0
|
||||
|
||||
is how you would configure the backupSnapshot.py and pruneIndexes.py programs to backup selected elastic search indexes, rotate selected indexes and prune certain indexes at selected intervals. In the case above we are backing up all indexes mentioned, rotating alerts monthly, rotating events daily and pruning events indices after 20 days.
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
aggregations = category1,category2
|
||||
aggregationthresholds = 200,120
|
||||
|
||||
is how you would configure eventStatsAlerts.py to alert you when you receive a 200% variance in events of category1 and a 120% variance in category2. All other categories will alert at a 100% variance by default.
|
||||
|
||||
::
|
||||
|
||||
[options]
|
||||
autocategorize = True
|
||||
categorymapping = [{"bruteforce":"bruteforcer"},{"nothing":"nothing"}]
|
||||
|
||||
is how you would configure collectAttackers.py to do autocategoization of attackers that it discovers and specify a list of mappings matching alert categories to attacker category.
|
||||
|
|
Загрузка…
Ссылка в новой задаче