- Instant OSSEC Host-based Intrusion Detection System
- Brad Lhotsky
- 162字
- 2021-08-13 16:28:01
How it works...
The simple configuration options we've specified for our server simply enable the secure communication over the UDP port 1514 between OSSEC clients and the server. We also configured the server to accept connections from our internal networks.
The best practice is to whitelist any IP addresses of potential agents as well as any known external business-critical resources. By whitelisting critical resources, we can ensure that OSSEC never interrupts service to those resources. Any resource that is critical in an emergency should be whitelisted, which is why we have whitelisted the external mail server.
Imagine being under attack and suddenly losing access to e-mail! The last two blocks configure OSSEC to send an e-mail on our network. If we need a specific SMTP server, we can tweak it here. Once we have our e-mail configured, we establish the thresholds for alerting at events whose level is 7
or higher. We will log any events whose level is 1
or higher.
- 數字身份與元宇宙信任治理
- Mobile Forensics Cookbook
- 網絡空間安全:管理者讀物
- 等級保護測評理論及應用
- 代碼審計:企業級Web代碼安全架構
- Kali Linux Wireless Penetration Testing Cookbook
- 局域網交換機安全
- 信息安全等級保護測評與整改指導手冊
- 網絡安全大數據分析與實戰
- 黑客攻防實戰從入門到精通
- Disaster Recovery Using VMware vSphere Replication and vCenter Site Recovery Manager
- 物聯網信息安全技術
- 功能型密碼算法設計與分析
- 網絡空間安全法律問題研究
- 數字銀行安全體系構建