Team1_LabReport2

.docx

School

Liberty University *

*We aren’t endorsed by this school

Course

461

Subject

Computer Science

Date

Dec 6, 2023

Type

docx

Pages

9

Uploaded by DeanBookPartridge8

Report
CSIS 461-001 Killian Boston, Marcus Jacobs, Gabe de la Torre- Garcia, Jacob Lohman Threat Hunting Log Consolidation Threat Hunting Analysis 2/12/22 Semester Week 5, Lab 2
Title Properly upgrade the Graylog server to ensure correct data. Consolidate all logs in Graylog for testing and threat hunting Download and implement Graylog on Windows, Linux, and PFsense Log forward various event logs such as security, system, application, and sysmon Record correct use of the Graylog system and any findings with the logs Analyze data collected and provide evidence of any potential cyber threats Abstract In this lab our team was required to update and activate the Graylog 4.1 server. Once the system was ready, log entries would be forwarded from at least two Windows and two Linux VMs. These logs are compiled together so that our team can search for potential Indications of Compromise from the red team, in both this lab and in the future. In order to complete this Graylog had to set up on CentOS and files had to be altered in both Linux and Windows to set up a proper connection. All information including logs and screenshots were recorded and presented in this lab report. All lab requirements were satisfied by our team. Introduction
This lab is split between 3 different Operating systems: Windows, Linux, and the Pfsense Firewall. From these three systems logs will be sent to a Graylog server. The logs can show a lot of helpful information about system, security, and application functions. The Graylog server will offer a centralized location for viewing the logs for various machines spanning multiple Operating systems. Method Install and upgrade Graylog server to 4.1 since 3.x does not work with elasticsearch 7.x Download the latest graylog packages online Use “sudo yum clean all” and “sudo yum update –y" to update the graylog server Use “sudo systemctl restart graylog-server" to restart the process and rpm to verify that version is updated Install nxlog and go to the nxlog.conf file, located at “C:\Program Files\nxlog\conf\nxlog.conf”
Within the nxlog.conf file and under the <Output out> section, change the host IP to the IP 192.168.1.251 (address of the Graylog server) Inside of “Windows Firewall with Advanced Security” create a new Outbound Rule Make the rule a Port Rule Type which applies to UDP with the specific remote port 1338 (nxlog’s port) Allow the connection and apply the rule to Domain and Private networks Name the new rule and go into its properties From the “Protocols and Ports” tab, make sure both the Local and Remote port are the specific 1338
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help