Downloaded 41 times
More Related Content
![[OPD 2019] Side-Channels on the Web:
Attacks and Defenses](https://cdn.slidesharecdn.com/ss_thumbnails/owasp-poland-day-tom-van-goethem-191021171917-thumbnail.jpg?width=640&height=640&fit=bounds)
Open Source Security
- 1. 大家好吗？大家好吗？ 我 是我 是Wim RemesWim Remes 比利时比利时
- 2. http://www.eurotrashsecurity.eu http://www.twitter.com/eurotrashsec Chris-John Riley, CraigBalding, Dale Pearson & me. (shameless self-promotion)(shameless self-promotion)
- 3. 今天的主题是今天的主题是 The value ofopen source solutions in a security infrastructure AN D
- 4. Infosec Technology in thepast decade
- 5. Pwned by avendor ?
- 6. It's time tounleash the power ...
- 7. What can't youdo with open source solutions?
- 8. YES WE CAN!YES WE CAN !
- 9. It's about thebottom line. Your bottom and Your line!
- 10. Open Source Security Ahost-based intrusion detection system
- 11. Mr. Daniel CidMr.Daniel Cid His royal OSSECnessHis royal OSSECness http://www.twitter.comhttp://www.twitter.com/danielcid/danielcid dcid in #ossec on irc.freenode.netdcid in #ossec on irc.freenode.net
- 12. OSSEC TechnicalOSSEC Technical OverviewOverview OSSECRollout ScenariosOSSEC Rollout Scenarios OSSEC Rule engineOSSEC Rule engine 1 2
- 13. Host Based IntrusionDetectionHost Based Intrusion Detection Client/Server ArchitectureClient/Server Architecture Highly ScalableHighly Scalable Cross PlatformCross Platform Log AnalysisLog Analysis Integrity CheckingIntegrity Checking Rootkit DetectionRootkit Detection Active ResponseActive Response 1 2 OSSEC Technical Overview
- 14. If a treefalls in a forest, andIf a tree falls in a forest, and nobody hears it, did it really fall?nobody hears it, did it really fall?
- 15.
- 16.
- 17. 1 2 customer 1 customer2 OSSEC Rollout Scenarios
- 18. And thy networkshall be namedAnd thy network shall be named BabelBabel
- 19.
- 20. 1 2 AGENT SERVER ossec-logcollector ossec-analysisd ossec-maild ossec-execd Compressed (zlib) Encrypted(blowfish) OSSEC Rule engine
- 21. Flexibility is thekey word here!Flexibility is the key word here!
- 22. 1 2 PRE-DECODING Feb 24 10:12:23Feb24 10:12:23 beijing appdaemon:stoppedbeijing appdaemon:stopped time/datetime/date :: Feb 24 10:12:23Feb 24 10:12:23 HostnameHostname :: beijingbeijing Program_nameProgram_name :: appdaemonappdaemon LogLog :: stoppedstopped OSSEC Rule engine
- 23. 1 2 Feb 25 12:00:47beijing appdaemon:userFeb 25 12:00:47 beijing appdaemon:user john logged on from 10.10.10.10john logged on from 10.10.10.10 time/datetime/date :: Feb 25 12:00:47Feb 25 12:00:47 HostnameHostname :: beijingbeijing Program_nameProgram_name :: appdaemonappdaemon LogLog :: user john logged on from 10.10.10.10user john logged on from 10.10.10.10 PRE-DECODING OSSEC Rule engine
- 24. 1 2 time/datetime/date :: Feb25 12:00:47Feb 25 12:00:47 HostnameHostname :: beijingbeijing Program_nameProgram_name :: appdaemonappdaemon LogLog :: user john logged on from 10.10.10.10user john logged on from 10.10.10.10 SrcipSrcip :: 10.10.10.1010.10.10.10 UserUser : john: john DECODING OSSEC Rule engine Feb 25 12:00:47 beijing appdaemon:userFeb 25 12:00:47 beijing appdaemon:user john logged on from 10.10.10.10john logged on from 10.10.10.10
- 25. 1 2 <rule id=666 level=”0”><ruleid=666 level=”0”> <decoded_as><decoded_as>appdaemonappdaemon</decoded_as></decoded_as> <description>appdaemon rule</description><description>appdaemon rule</description> </rule></rule> <rule id=”766” level=”5”><rule id=”766” level=”5”> <if_sid>666</if_sid><if_sid>666</if_sid> <match>^<match>^logged onlogged on</match></match> <description>succesful logon</description><description>succesful logon</description> </rule></rule> ANALYSIS OSSEC Rule engine
- 26. 1 2 ANALYSIS <rule id=866 level=”7”><ruleid=866 level=”7”> <if_sid>766</if_sid><if_sid>766</if_sid> <hostname>^beijing</hostname><hostname>^beijing</hostname> <srcip><srcip>!192.168.10.0/24!192.168.10.0/24</srcip></srcip> <description>unauthorized logon!</description><description>unauthorized logon!</description> </rule></rule> <rule id=”966” level=”13”><rule id=”966” level=”13”> <if_sid>766</if_sid><if_sid>766</if_sid> <hostname>^shanghai</hostname><hostname>^shanghai</hostname> <user><user>!john!john</user></user> <description>unauthorised logon !</description><description>unauthorised logon !</description> </rule></rule> OSSEC Rule engine
- 27.
- 28. 1 2 ANALYSIS <rule id=1066 level=”7”><ruleid=1066 level=”7”> <if_sid>666</if_sid><if_sid>666</if_sid> <match>^login failed</hostname><match>^login failed</hostname> <description>failed login !</description><description>failed login !</description> </rule></rule> <rule id=”1166” level=”9”<rule id=”1166” level=”9” frequency=”10” timeframe=”100”frequency=”10” timeframe=”100”>> <if_matched_sid>1066</if_matched_sid><if_matched_sid>1066</if_matched_sid> <same_source_ip /><same_source_ip /> <description>Probable Brute Force !</description><description>Probable Brute Force !</description> </rule></rule> OSSEC Rule engine
- 29. 1 2 AGENT SERVER ossec-logcollector ossec-analysisd ossec-maild ossec-execd Compressed (zlib) Encrypted(blowfish) OSSEC Rule engine
- 30.
- 31.
- 33. 谢谢谢谢 Thank youThank you wim@remes-it.bewim@remes-it.be(mail)(mail) blog.remes-it.be (blog)blog.remes-it.be (blog) @wimremes (twitter)@wimremes (twitter) #ossec (irc)#ossec (irc)