Jeethan's CL-CY-001 course work. Lv 3

Jeethan's MARVEL Level 2 Tasks Report : Part 1

1 / 4 / 2025

Click here for the github repo

TASK 1: CI/CD (Continuous Integration & Continuous Delivery) - Intro to Jenkins

What did I learn?

• In this task I basically learned about what CI/CD is and learnt how it is useful in practical industry level development
• CI/CD is nothing but a working model which helps in increasing the speed of development and reduces bugs and fault in code
• I learn about different models that have been in the history of industry such as the Waterfall model which was the oldest model of development used in the 90's, then came the Agile model which was used in the early 2000's, but finally in the late 2000's a new model was adopted called as DevOps model here the Developers and Operations team work together and complete a feedback loop which helps in faster development and more reliable code
• So to speak about this in detail, CI/CD and DevOps are closely related, CI is continuous integration and CD is continuous development. CI is basically continuosly uploading to a repo and CD is basically deploying the code
• DevOps is basically using CI/CD and breaking down the project into smaller projects and working on them
• 
• Now to setup the DevOps model we have a helper, this helper is called as Jenkins
• So Jenkins is nothing but an automating software that helps in CI/CD we have to basically script a code in GROOVY language and then we are done, Jenkins automatically detects new code we write , pulls it from the repo, tests it and then finally deploys it, its that easy
• 
• 
• 
• 
• 

TASK 2: Terraform

What did I learn?

• So the first thing I learn in this task was about what EC2 was, how does it work and what it exactly is
• Also i learned about AMI (amazon machine images), these are basic images of OS such as ubuntu, macOs , linux etc which we can use to create EC2 instances
• I learned more about AWS and I learnt how it works
• I also learned how to make an EC2 instance using the AWS website
• Terraform is basically IaaC (Infrastructure as Code)
• So, its basically used to make infrastructure such as EC2 instances and manage them and also configure them using basic declarative code
• I learned basic commands such as :

 terraform init 
 terraform plan 
 terraform apply 
 terraform destroy

• terraform init – Initializes Terraform in your working directory.
• terraform plan – Previews the changes Terraform will make.
• terraform apply – Executes the changes and provisions the infrastructure.
• terraform destroy - Destroys the instances
• So I made EC2 instances and also made a basic Apache webserver using Terraform
• 
• 
• 
• 
• 
• 
• 
• 

TASK 3: Wireshark

What did I learn?

• I learned that Wireshark is an open-source network protocol analyzer widely used to troubleshoot network issues, analyze network packets, and perform security auditing and also learnt its use cases.

  • Packet capture: Wireshark can capture traffic using your network interface.
  • Protocol analysis: Wireshark supports the decoding and analyzing of over 3000 network protocols so you can understand their structure and content.
  • Packet filtering: Wireshark includes powerful display and capture filters that filter network traffic.
  • Network packet reconstruction: Wireshark can reconstruct network packets to display application-level protocols so you can see web pages, images, or other application data.
  • Network traffic statistics and visualizations: Wireshark provides statistical data and visualizations of network traffic.

• I leaned about TLS and SSL, TLS is Transport Layer Security which is a cryptographic security provided to protocols in the transport layer for example HTTPS, so https is secure due to TLS, SSL is Secure Socket Layer, it is just an outdated version of TLS

• I learnt basic working of Wireshark and to use its tools:

  1. Adding Filters
     • Lets you focus on specific packets by filtering out unnecessary traffic.
     • If you only want to see HTTP traffic, you can use the filter http instead of browsing through thousands of packets.
  2. Using Statistics (Conversations, Protocol Hierarchy, IO Graphs, etc.)
     • Helps analyze traffic patterns by summarizing different aspects of network communication.
     • You can check which protocols (like TCP, UDP, HTTP) are used the most, see which devices are talking to each other, and visualize traffic trends over time.
     • Different Statistics in Wireshark
       • Wireshark provides several statistical tools that help analyze network traffic patterns. These tools summarize data, making it easier to spot issues, understand traffic flow, and optimize network performance.

         1. Packet Lengths : Shows the distribution of packet sizes in your network capture. Helps identify abnormal packet sizes. For example, too many very small packets might indicate inefficient communication, while unusually large packets could be a sign of data exfiltration or an attack.

         2. Protocol Hierarchy : Breaks down traffic by protocol (e.g., HTTP, TCP, UDP, DNS).Shows what percentage of traffic each protocol is using. if you see too much HTTP traffic, it may indicate heavy web browsing, while a high percentage of DNS requests could signal malware or misconfigurations.

         3. Conversations : Lists all communication between two devices (IP or MAC addresses).Shows the number of packets exchanged, total bytes sent, and duration of communication. Can be used to detect suspicious or long-lasting connections, which may indicate data leaks or malware.

         4. Endpoints : Lists all devices (endpoints) communicating on the network. Shows each device’s IP address, MAC address, packets sent, and total data exchanged. Helps identify unknown devices on a network.

         5. IO (Input/Output) Graphs : Graphs network traffic over time to visualize trends. Useful for spotting traffic spikes that may indicate DDoS attacks, data downloads, or streaming activity.

         6. Flow Graphs : Displays a step-by-step flow of communication between two hosts. Helps debug slow responses, failed connections, or retransmissions.

  3. Following Streams
     • Reconstructs an entire conversation (TCP, UDP, HTTP, etc.) between two devices.
     • If you want to see a full exchange between a computer and a server, you can "follow" the conversation instead of viewing individual packets separately.
  4. Color Coding
     • What it does: Highlights packets with different colors to make different types of traffic stand out.
     • Use case: Red may indicate TCP errors, green might show normal traffic, and black could signal serious issues like lost packets.

• 

• 

• 

• 

• 

• 

• 

Click here for part 2