▶ SUMMARY:The first third of the year was spent improving the quality of the XD Bridge ST product. I developed a script to gather all possible raw log message information and generate a spreadsheet where they could be reviewed for improving clarity and consistency for communication to the user. I improved XML filters to better handle data in transit and avoid attacks. I resolved several critical memory leaks and mismanagement issues throughout data pipeline components. I served as a Quality Assurance Engineer for a formal regression test cycle of ST. The majority of the year was spent developing GUI menus for 4 different user roles of the V2 CDS product.▶ HIGHLIGHTS:🔹 Authored a Bash script for gathering all raw log message information throughout the ST codebase and generating a Microsoft Excel spreadsheet to aid in reviewing them for improving clarity and consistency.🔹 Updated XML filters in C and C++ of the XML data pipeline for improved handling of data in transit and to avoid attacks such as the "billion laughs attack."🔹 Discovered, investigated, and resolved critical memory leaks and memory mismanagement issues found throughout ST data pipeline components and utility tools using gdb, valgrind, top, atop, htop, and C.🔹 Served as an on-site Quality Assurance Engineer for conducting formal ST regression testing using test plans and sample data.🔹 Developed 4 GUI menus in Java for different user roles of the V2 CDS product for configuring new data pipelines, securely uploading config files for pipeline assignments, generating a truststore and keystore, and more.

▶ SUMMARY:I made a final major improvement to the Remote, Journaling, & Auditing Transfer (RJALT) component of the Journaling, Auditing, & Logging Subsystem (JALS) of the XD Bridge ST product for improved JAL data handling. I authored a new utility tool for creating standardized log messages for all ST components to use. I assisted in rearchitecting the TCP Adapter component for improving its connection management. I authored a script for packaging all technical security reports for all components of ST as a deliverable for an overall security assessment of the product. I discovered and resolved dozens of SECCOMP issues that arose for several ST components. My final development efforts of the year went toward creating a new JALS from scratch for the V3 CDS product under a tight time constraint.▶ HIGHLIGHTS:🔹 Updated the RJALT using C to support bidirectional communication with its TCP Adapter component to avoid data loss if a connection should be lost and to communicate reconnection attempts🔹 Developed the JAF-Styler component as a utility tool for all ST components to standardize the format of log messages that would be sent to the CALD for validation and further routing🔹 Assisted with rearchitecting the TCP Adapter using flow diagrams, PlantUML, and, ultimately, C for having an improved handling of connection management with remote systems.🔹 Authored a Bash script for remotely pulling down all latest source code of ST components, generating accurate Coverity security report documents for each component, and packaging them up as a zipped TAR file🔹 Discovered and resolved several SECCOMP issues in ST components using system audit logs and C.🔹 Co-developed a web-based GUI using HTML, CSS, and JavaScript with Vue.js, Electron.js, and Bootstrap as a Proof-of-Concept for a modernized GUI XD Air product.🔹 Developed a new CALD, LJALS, and RJALT using Java for a new JALS of the V3 CDS product under a tight deadline.

▶ SUMMARY:This year, I was primarily focused on continuing development for the XD Bridge ST product. My initial efforts pertained to continuing the development of the Journaling, Auditing, & Logging Subsystem (JALS) of the ST product. I led the ST development team on defining a standardized messaging format to satisfy security requirements for ST that would be asserted by the JALS. Later in the year, I focused on resolving critical memory leaks of data pipeline components that would hinder long-term use of ST. My final development efforts of the year were on the Full Motion Video (FMV) pipeline of ST for improving the handling of video quality and developing a new filter for validating Key-Length-Value (KLV) data of videos in transit.▶ HIGHLIGHTS:🔹 Refactored the CALD into the LJALS and RJALT, both in C. The LJALS would be responsible for growing log files for each ST component as well as managing archiving and aging of them. The RJALT would be responsible for transferring received JAL data to a remote Syslog server via UDP, TCP, TLS, or REST.🔹 Devised a standardized messaging format in XML for all ST components to use for communicating to each other. This would allow for uniform validation and parsing techniques by JALS components I authored.🔹 Resolved critical memory leaks in data pipeline components written in C and C++ using tools such as gdb, valgrind, top, atop, and htop.🔹 Improved the video quality handling of the FMV pipeline, specifically at the level of MPEG transport steam (TS) packets🔹 Authored the KLV filter for validating KLV data from a video in transit and ensuring that certain tags were included when expected.

▶ SUMMARY:After completing the initial design and development plan documentation for a centralized logging daemon of the XD Bridge ST product, I implemented the Centralized Auditing/Logging Daemon (CALD) component. Following this, I implemented an XML parsing and validation utility tool for all components of ST to use. Later on, I developed the backend for the ST GUI menus, the Action Engine, as well as system-level wrappers, OwlSysWrappers. The Action Engine would utilize OwlSysWrappers for making system-level configuration changes.▶ HIGHLIGHTS:🔹 Developed the CALD using C for receiving journal, audit, and log (JAL) data from ST data pipeline components via POSIX message queues, managing local log files for each ST component, and remotely transferring JAL traffic to a remote Syslog server via UDP or TCP🔹 Developed OwlProcXml using C and libxml2 for validating and processing XML data which became utilized by all ST components for receiving standardized messages. Some validation code was originally leveraged from owlXERCES, written in C++, that used Apache Xerces.🔹 Developed the Action Engine backend handler of the ST GUI menus Menu Engine component for performing system-level configuration changes such as networking management, offloading of JAL data to a disc, and setting hostname information🔹 Developed OwlSysWrappers, utilized by the Action Engine, but made available for other products, for performing system-level configurations🔹 Authored and maintained Confluence webpages covering how to use owlProcXml as an API for ST components written in C/C++, the development process for the Action Engine, and the development process for creating a new system wrapper within the OwlSysWrappers project space

▶ SUMMARY:I started my software engineering career this year as an Associate Software Engineer. I hit the ground running during my first week by planning low-level development for the Logging Manager (LM) component of the new Cloud-to-Cloud (C2C) secure file transfer product. After completing development of the LM, I made software updates to the Owl Perimeter Defense System (OPDS) for its 2.0.2.0 release that pertained to its menus, files on a Linux-based system, and data transfer components. The third product I developed was the web-based Owl Performance Management Service (OPMS) for its 2.6.7.0 release. I concluded the year starting documentation for a centralized logging daemon of a future product, the XD Bridge ST.▶ HIGHLIGHTS:🔹 Developed the Logging Manager (LM) component of C2C using C for being a centralized receiver of log traffic from C2C components that would manage component-specific log files locally and transfer to a remote Syslog server.🔹 Conducted quality assurance testing on the C2C menus and data pipelines to ensure compliance with the use-case matrix of product requirements.🔹 Updated the Security Controls Testing Procedures documentation for C2C to ensure there is a product response for each expected security feature🔹 Developed the Owl Perimeter Defense System (OPDS) for its 2.0.2.0 release using Python and C for GUI menu updates, backend menu handling of system configurations, and improvements to data transfer components.🔹 Developed the Owl Performance Management Service (OPMS) for its 2.6.7.0 release using HTML, CSS, JavaScript, PHP, Perl, and Python. Additional web tech used: AJAX, jQuery, Dojo, Dijit, GET/POST HTTP requests.

I collaborated with several groups working on various gaming projects and offered design suggestions. I attended several "sprint" meetings where developers could share their current progress with their teammates. I shadowed people of different Scrum roles.