Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cyber Threat Intelligence Dashboard #1101

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Conversation

Ananya-vastare
Copy link
Contributor

Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.


Issue Title

Please enter the title of the issue related to your pull request.
Enter the issue title here.
Cyber threats intelligence dashboard.

  • I have provided the issue title.

Info about the Related Issue

What's the goal of the project?
The goal of the project is to provide an interactive dashboard for cyber threat intelligence, allowing users to visualize and analyze recent threats, alerts, and other relevant data to enhance cybersecurity awareness and response.

Describe the aim of the project.
The aim of the Cyber Threat Intelligence Dashboard project is to create an interactive and user-friendly platform that aggregates and visualizes data related to cyber threats. This dashboard is designed to help cybersecurity professionals and organizations monitor, analyze, and respond to potential threats effectively.

  • I have described the aim of the project.

Name

Please mention your name.
Enter your name here.
Ananya Ravikiran Vastare

  • I have provided my name.

GitHub ID

Please mention your GitHub ID.
Enter your GitHub ID here.
@Ananya-vastare

  • I have provided my GitHub ID.

Email ID

Please mention your email ID for further communication.
Enter your email ID here.
[email protected]

  • I have provided my email ID.

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
GSSOC-extd

  • I have mentioned my participant role.

Closes

Enter the issue number that will be closed through this PR.
Closes: #issue-number
#1045

  • I have provided the issue number.

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
I have developed a Cyber Threat Intelligence Dashboard using Streamlit that provides users with a comprehensive view of cyber threats. The dashboard features functionalities for data visualization, including interactive plots that display trends in threats over time. I implemented a data search feature that allows users to filter threats based on specific keywords in their descriptions. Additionally, I added static datasets to replace API calls for data retrieval, ensuring the application is self-contained and easy to run without reliance on external APIs. The code has been structured for clarity and maintainability, with comments added for better understanding.

  • I have described my changes.

Type of Change

Select the type of change:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, local variables)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Describe how your changes have been tested.
Testing Process:

I tested the Cyber Threat Intelligence Dashboard by running the application in a local development environment using Streamlit. I verified the functionality of data visualization features by ensuring that the interactive plots correctly displayed trends based on the provided static datasets. I also tested the search functionality to confirm that it accurately filters results based on user input. Additionally, I conducted usability testing by navigating through the dashboard to ensure all components functioned as expected and the user experience was seamless. Finally, I reviewed the code for any potential errors and validated that it met the project’s coding standards, generating no new warnings during execution.

  • I have described my testing process.

Checklist

Please confirm the following:

  • My code follows the guidelines of this project.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly wherever it was hard to understand.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • I have added things that prove my fix is effective or that my feature works.
  • Any dependent changes have been merged and published in downstream modules.

Copy link

github-actions bot commented Nov 5, 2024

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!

@UTSAVS26 UTSAVS26 added Contributor Denotes issues or PRs submitted by contributors to acknowledge their participation. Status: Review Ongoing PR is currently under review and awaiting feedback from reviewers. level1 gssoc-ext labels Nov 5, 2024
Copy link
Collaborator

@ruhi47 ruhi47 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@ruhi47 ruhi47 added Status: Approved PRs that have passed review and are approved for merging. and removed Status: Review Ongoing PR is currently under review and awaiting feedback from reviewers. labels Nov 7, 2024
@UTSAVS26 UTSAVS26 merged commit 3504016 into UTSAVS26:main Nov 7, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Contributor Denotes issues or PRs submitted by contributors to acknowledge their participation. gssoc-ext level1 Status: Approved PRs that have passed review and are approved for merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants