This week, the team Splunkernauts have successfully finalized everything and are ready to present the project next week. We finished our documentation, poster, promotional video, and are actively working towards finalizing our notebooks.

Team Splunkernatus is eagerly waiting to present our project next week and impress our coaches and liaison by successfully meeting all of their requirements from this project.

CC: FINAL VERSION OF THE POSTER

This week, Team Splunkernauts successfully implemented the feedback we received last week. We successfully made a final version of our poster before feedback from our classmates. We finalized our promotional video. We are excited to present the project in 2 weeks.

Next week, we plan. on finalizing the poster and the documentation to present to our liaison. Finalize our preparations for FDR!

CC: Our poster for FDR

This week, team Splunkernauts went all out on their grind. We conducted a User-test of the dashboard by students in a cybersecurity class that Dr.Resch teaches. She allowed us the opportunity to present in her class. Following that we did our PID presentation and it went well and in both cases we received positive feedback to work with and implement into our presentation and project.

Next week, our team will be focused on implementing the feedbacks we got, continue working on our documentations and start the poster for presentation.

CC: USER TESTING RESULTS with a positive score from Dr.Cheryl’s classroom

This week, the Splunkernauts team made significant strides in the video graphing component of our project, progressing nearly halfway towards completion. The remaining task involves the meticulous editing phase, which we aim to wrap up by the week’s end. Meanwhile, on the technical front, we enhanced our Triggered Attacks Over Time & Attack Types chart by incorporating additional filtration status and labels, ensuring comprehensive data representation.

Looking ahead, our objectives for the upcoming week are twofold: finalize the video editing process and commence the compilation of project documentation. With these endeavors, we endeavor to culminate our project journey on a comprehensive and polished note, ready to present our accomplishments with clarity and finesse.

CC: Improved versions of “Triggered Attacks Over Time” & “Attack Types” visual charts

This week, the diligent efforts of the Splunkernauts team bore fruit as we successfully implemented a submit button feature within the system. This enhancement enables users to trigger information retrieval explicitly, conserving vital processing power by eliminating continuous background operations. This strategic refinement ensures optimal performance of the dashboard, enhancing efficiency and user experience.

Looking ahead to the upcoming week, our focus shifts towards commencing the video component of the project, a pivotal element for the final presentation. Concurrently, we are committed to integrating additional filter features into our charts based on recently unearthed edge cases, further enriching the system’s analytical capabilities and refining its capacity to address diverse scenarios.

CC: Successfully added and functionable “Submit” button for searches.

This spring break week, the team indulged in moments of relaxation while also channeling their creative energies into enhancing the UI design. After exploring various design iterations, we opted to reposition textual information to the bottom and incorporate an eye-catching image featuring the RTX logo image with a flag, aiming to captivate users visually.

Looking ahead to the forthcoming week, our focus will be on refining the search functionality by introducing a submit button feature. Additionally, we plan to conduct thorough research to address any potential edge cases related to attack scenarios, ensuring comprehensive coverage and robust system readiness.

CC: New visual presentation design of Splunk Dashboard

This week, the Splunkernauts team dedicated efforts to enhance the system’s search features for potential attacks, aiming to provide clearer insights. We introduced a new dropdown named “Attack(s),” currently in development and not yet finalized. However, it plays a vital role in identifying prevalent attacks and their resolution status. This tool empowers users to prioritize security measures effectively, focusing on areas needing heightened protection.

Looking ahead, our focus shifts to refining the dashboard’s visual presentation to further elevate user experience and comprehension. We eagerly anticipate the possibilities this enhancement may unveil in the coming week.

CC: Dropdown labeled Attack(s) with options being All, Not Defined, & Potential_Attack to search for!

This week, the Splunkernauts team had a great meeting where we presented our progress in QRB2. We worked hard to improve our filter features, but ran into some trouble because of how our data is set up. After a lot of troubleshooting and research, we managed to get everything working smoothly.

Now, we’re waiting to hear back from RTX to help us with the last couple of challenges. We’re excited to keep working on making our UBA and UI/UX design even better and more innovative.

CC: Filter features Priority & Status

In the past week, our team Splunkernauts focused on making our dashboard UI more user friendly by adding more visuals in the form of charts and graphs with alerts and attacks information. Our team is currently focused on making our QRB2 presentation outstanding to our coaches and judges. Our goals for this and next week are to improve our documentations and check for UBA on printing activities.

CC: Added two types of charts; 1. Alerts over time. 2. Attack Types.