Category: Vessel Page 1 of 2

Micah, holding a fish on the beach.

Introduction- Micah Barton

Voyage Beginnings – 01

Hello sailors and scallywags! My name is Micah Barton. I am a recent graduate of Cape Fear Community College, with an associates degree in Marine Technology. The privilege of a high quality education has forever changed my life for the better, and I have developed a deep love and passion for marine sciences. Every moment has been wonderful, from surveying in the rain, watching sharks circle the trawl, troubleshooting software for hours, and even to counting thousands of shrimp- fantastic. I can’t imagine my life without it. I have an amazing crew of educators and classmates that have worked tirelessly and pushed me to make it this far; I work hard every day to make them proud!

This is a picture of my last cruise at CFCC aboard the R/V Cape Hatteras. Since day one of sailing, I knew that there was no going back for me- life at sea or bust! Like countless others before me, I have felt the breeze on my cheek and heard the voice of the sea;

Voice of the sea that calls to me,
Heart of the woods my own heart loves,
I am part of your mystery—
Moved by the soul your own soul moves.

Dream of the stars in the night-sea’s dome,
Somewhere in your infinite space
After the years I will come home,
Back to your halls to claim my place.

by William Stanley Braithwaite

Here I am! I love to fish, explore, and create. I will be starting my internship on the R/V Thomas G. Thompson. Through this blog I hope to share my journey, my perspectives, and the things I learn along the way. Thank you for joining me, and I can’t wait to see what the future holds!

Micah Barton – 04/21/2025

Final Dispatch from the RV Sikuliaq – Cybersecurity in the Wild

The SECURE-IT cyber training cruise aboard the R/V Sikuliaq has come to an end, and I’m writing this final post while taking in the cold Alaskan air after days of navigating the Pacific. It’s hard to put into words how transformative this experience has been, both technically and personally.

Each day onboard was a full-immersion dive into maritime cybersecurity and cyberinfrastructure. We configured segmented networks using Fortinet firewalls, utilized Proxmox virtual environments, and worked with legacy systems still commonly found in real-world maritime operations. We tackled bandwidth limitations, satellite communications, and network segmentation in a way that mirrored actual at-sea constraints—and that’s not something you can fully simulate in a classroom.

One of the most impactful parts of this experience was the people. Having such a diverse crew—ranging from seasoned technologists and marine technicians to undergraduate students from across the country—created an environment rich in what’s known as tacit knowledge. These are the kinds of insights that aren’t always written down—techniques, workarounds, and instincts that come from time spent in the field. Watching the experienced professionals troubleshoot or explain their setups gave me a much deeper appreciation for the human element in technical problem-solving.

Another standout for me was having Tyler Peterson, a former MATE intern, onboard. His background as a marine technician and his experience with more traditional MATE internships helped bridge the gap between the classic marine tech path and this first-of-its-kind cruise focused on Information Technology, cybersecurity, and cyberinfrastructure. While we weren’t supporting an active science mission during this cruise, Tyler helped connect the dots between shipboard IT systems and how they ultimately enable and support scientific research. That context was incredibly valuable—it made the purpose behind the tech we were building feel real and relevant.

Something else that really stuck with me: it takes a variety of disciplines to make scientific research at sea possible. From satellite communications and data acquisition systems to physical deployments like the ARGO floats, the cruise was a reminder that meaningful science only happens when engineers, IT professionals, technicians, and scientists work in harmony. This cruise wasn’t just a training exercise—it was a snapshot of what that collaboration can look like in action.

One of the personal highlights: I earned three cybersecurity certifications during this cruise—two from Fortinet and one awarded by the R/V Sikuliaq team. These credentials not only boosted my technical skill set, but also marked a real milestone in my journey toward becoming a cybersecurity professional in the maritime world.

Massive thanks to the University of Alaska Fairbanks (UAF) for hosting, Fortinet for the technical resources, the MATE program for making this internship possible, the crew of the R/V Sikuliaq, and everyone who made this adventure happen. Special shoutout to Julian Race for leading the charge and creating space for real hands-on learning. I’m leaving this cruise sharper, more inspired, and more confident in my future as a cybersecurity professional in the maritime space.

Until next time—signing off from the Gulf of Alaska.

Cybersecurity at Sea – Aboard the R/V Sikuliaq

Hello! I’m currently writing from my newly designated workstation aboard the R/V Sikuliaq, docked at the University of Hawaiʻi Marine Center in Honolulu, Hawaiʻi. We are scheduled to get underway later this evening. The Sikuliaq, operated by the University of Alaska Fairbanks, is a 261-foot ice-capable research vessel, and our current expedition—SEACURE-IT—is focused on advancing cybersecurity practices in maritime environments.

Our mission centers on understanding and strengthening shipboard cybersecurity infrastructure. Today’s focus was building a simulated research vessel network using Fortinet hardware, including a FortiGate next-generation firewall and a FortiSwitch managed switch. Each virtual vessel was named after a Star Trek captain, and I’m pleased to report that the R/V Christopher Pike is now fully operational.

To bring the system online, we began by installing the firewall and switch hardware, gaining access through the serial console port. From there, we configured a VLAN (Virtual Local Area Network) and assigned appropriate switch ports. After establishing basic connectivity, we implemented firewall rules to enable WAN access for the VLAN while maintaining strict segmentation between networks.

One of the critical lessons in maritime cybersecurity is the need to separate Information Technology (IT) systems from Operational Technology (OT). Onboard vessels, OT systems (such as industrial controllers managing propulsion, navigation, and critical mechanical systems) are sometimes based on legacy architectures and lack modern security hardening. Allowing these to share a network with IT systems—or worse, exposing them to the internet—creates serious vulnerabilities. Our firewall policy design reflects this reality, ensuring the IT and OT VLANs remain isolated. It is also best practice to separate these networks so that everyday users do not accidentally interfere with critical operations.

After confirming secure internet access on the IT VLAN, we deployed a lightweight Ubuntu virtual machine using the Proxmox hypervisor. While running on limited hardware, the system performs well thanks to the efficiency of Ubuntu, enabling us to simulate key cybersecurity operations within our constrained environment.

To put our network control to the test, I implemented a multi-layered blocking policy targeting a known security concern: TikTok. Using FortiGate’s Application Control, DNS Filtering, and Web Filtering capabilities, I successfully restricted access to TikTok domains and traffic patterns. As a result, no devices on our network can currently access the platform—a practical example of layered defense and policy enforcement in a live environment.

This experience has already been invaluable. I’m gaining exposure not only to enterprise-grade network security tools, but also to the nuances of securing mission-critical systems aboard research vessels.

Introduction – RaymondJames

Hello, I’m RaymondJames Gallant, a cybersecurity student at Eastern New Mexico University and a 2025 MATE intern. I’ll soon be embarking on a cyber internship aboard the RV Sikuliaq, where I’ll be learning firsthand how cybersecurity supports maritime research and operations. I’m passionate about protecting critical infrastructure and excited to explore the intersection of technology and ocean science. I’ll be using this blog to document my experiences, growth, and reflections throughout the journey—thanks for following along!

Internship Overview – Ethan

Hello everyone,

I’ve spent the past week aboard the Marcus G. Langseth, gaining valuable exposure to its unique labs and state-of-the-art oceanographic equipment. On my first day, I had the opportunity to tour several areas of the ship, including the Main, Wet, Dry, and Port Labs, as well as the Gun Shop, Bird Shack, and Muster Station. Each of these spaces offered insight into the operations and specialized functions aboard the vessel.

Throughout the week, my fellow interns and I worked closely with our mentor, Cody Bahlau, on a variety of tasks around the ship. One of the daily activities we assisted with was performing the BIST for the swath mapping sonar, ensuring its functionality, and resetting the weather station.

I also participated in the weekly gravity check and gravity tie, a critical task to ensure that the gravimeter remains properly calibrated and provides accurate readings. To complete the gravity tie, I traveled to the pier where the Land Tie was performed. Since tide height can vary, we took measurements from the pier to the water at three different stages: when the tie began, at 50% completion, and when it finished. This process allows us to account for the tide’s effect on the gravity measurements. Once the gravimeter was confirmed to be working accurately, we carefully prepared it for transport by placing it into its protective case, securing its batteries, and carefully moving it up to the Wet Lab, all while ensuring it remained powered throughout the process.

In addition to the technical tasks, we were also involved in some practical maintenance work. We helped secure loose items on deck in preparation for transit, organized and restocked personal protective equipment (PPE), and spent a considerable amount of time over two days cleaning and constructing new desk spaces for the Dry Lab. Building these desks was an unexpected yet highly rewarding experience. Because the ship’s environment requires extra durability, we made sure the desks were sturdy enough to withstand movement and could be securely bolted to the floor. To accomplish this, we used metal framing for the desk skeleton, ensuring it could be anchored to the ship’s floor. We then cut and fitted the top, side, and back panels to add further stability, improve the overall aesthetic of the lab, and hide wires and cables. This hands-on project allowed me to work with various power tools, including a chop saw, angle grinder, and buzz saw—skills I was excited to develop.

Overall, this experience has been a fantastic blend of technical work and practical skills, giving me the chance to work with cutting-edge equipment and learn valuable hands-on techniques. Unfortunately, due to changes in the ship’s transit schedule and an extended length of travel, I won’t be able to stay aboard the Langseth for its journey to Cape Verde. Nevertheless, this has been an unforgettable experience, and I truly hope I’ll have the opportunity to work aboard a vessel as impressive as the Marcus G. Langseth again in the future.

Week 3 – Arriving at Cape Verde/ End on Internship – Will

Hello for the last time from the R/V Langseth! As I am writing this, I am about 100 nautical miles from arriving at the island of Sao Vicente, part of the Cape Verde archipelago! While my time aboard the Langseth has been relatively short, it has been nothing short of an amazing and worthwhile experience that I would heavily recommend participating in should you have the opportunity!

Early in the week, Theo and I tackled revisions to the DigiBird calibration manual, making it more concise, structured, and user-friendly. We wanted future users to have a clearer, more streamlined guide, and we’re confident our updates will make troubleshooting much easier.

Midweek, we turned our attention to inventorying our equipment, unpacking and inspecting 56 old and new Niskin bottles for damage before organizing them into labeled palletainers. I also got my first experience calibrating Acoustic Pingers, which are much easier to work with compared to DigiBirds. Acoustic Pingers are an essential component of the Langseth’s streamer deployment, as they communicate with not only one another, but also the ship, relaying critical information as to where exactly the streamer currently is in the water. Working up in the protected species observer tower was a nice change of pace—removing and recalibrating Vaisala weather station antennas gave us a reason to soak up the fresh ocean air while still getting things done.

A major highlight of the week was learning about streamer deployment and seismic data acquisition. We unspooled a streamer on deck, attached LAUMs (Line Acquisition Unit Modules), and got hands-on experience using the SEAL 428 seismic recorder system. It was fascinating to see how hydrophone data is converted from analog to digital and how external noise sources, like fishing gear and passing ships, can interfere with data collection.

To end the week, Theo and I tackled the task of replacing the Digibird motor modules that were either bad or paired with bad electronic modules. Cody had recently taught us how to do so, so this allowed us to put his teaching into practice, which we did with great effectiveness! To replace a motor module requires essentially stripping the Digibird of all its interior components, requiring very cautious exactness and patience in order to ensure we do not damage any components during a motor swap.

We were able to complete either a motor swap or a complete haul of every component on every bird we aimed to, allowing us to finish our internship with a great sense of achievement and set the next set of interns up for success, as we tested all spare motors to find which were good and bad so they didnt have to! I can say for sure, I am adept in all things relating to the calibration and troubleshooting of Digibirds!

Thank you for keeping up with my weekly posts, it has been a pleasure sharing the amazing experience I have had. I also want to give a huge thank you to Chief Science Officer and my mentor, Cody Bahlau, for his dedication in seeing that Theo and I succeed, thrive, and take as much advantage of this opportunity as possible. And of course, a huge thank you to the UNOLS-MATE Program Manager Maria Osiadacz for making this opportunity possible and being such a wonderful support throughout the entire internship!

Wishing you the best,

Will

Week 3 — Closing in on Cabo Verde — Theo

We’re finally closing in on Mindelo in Cabo Verde! We get in tomorrow morning at around 6am, and after that I am headed back to San Diego. This past month has flown by, and I’m super grateful to have had this opportunity—I feel like I have learned so much. I’m looking forward to staying in touch with the technical team and participating in similar opportunities down the line!

Now let me catch you up to speed on this past week. And when I say catch you up to speed, only one thing comes to mind: birgatory. We spent a lot of time working in the Bird Shack this week, and we started off pretty easy working on the Acoustic Pingers. These instruments are very similar to our digibirds except they’re a whole lot simpler: they basically just ping the boat to let us know the location of the streamers in the water behind us. All we had to do was recalibrate them and recharge their batteries. We were bumped up a level in difficulty, however, when we started working on the digibirds with bad motors. This took FOREVER. Let me walk you through testing one bird: you dismantle the bird, carefully dismantle and pull out the compass module, push out the motor and the electronics modules, carefully disconnect the motor from the electronics, carefully reconnect a new motor back to the electronics, reinsert both modules back in the bird, put the whole bird back together, and finally retest the motor functionality. If the bird still doesn’t work, you troubleshoot it by redoing that process all over again with a different motor. If both motors aren’t working, then the electronics module was bad, which meant stripping the bird for parts and retesting both the original and replacement motors. It was definitely hard work and ever-so-slightly mind numbing. At the end of the day, however, (and maybe because I never have to do it again) I can tell you that it was definitely a valuable learning experience for me. In any opportunity moving forward, I know I can calibrate, troubleshoot, and repair sensitive scientific equipment, even if I know very little about the instrument to begin with.

Speaking of sensitive equipment, perhaps the highlight of my week was getting the chance to run through troubleshooting our streamers. We finally got to test out one of the streamers on deck, unspooling the very end before screwing in a few LAUMs (line acquisition unit modules). Following that, we moved downstairs to learn how to read and interpret the data from the hydrophones, and how to troubleshoot the system if something goes wrong. It was super super interesting, and I would love to get more experience doing data analysis and troubleshooting in the Main Lab control room in the future. The program the Langseth team uses, SEAL, models all the data being transmitted from each individual hydrophone along the entire 15km line, as well as every LAUM and FDU (field digitizing unit). This amounts to five hundred something hydrophones for each streamer, half that many FDUs, and a couple dozen LAUMs. It’s pretty incredible technology and was great to experience so closely.

I’d say my final highlight of the week was working up on deck, familiarizing myself with Niskin Bottles and working on the Vaisala Weather stations. This scientific equipment aligns a lot more closely with my own personal interests in biological oceanography, and after a few weeks it was interesting taking a little break from seismology. While we didn’t actually get to apply either of these instruments, I did become pretty familiar with how to take them apart and put them back together again. If I’ve learned anything from this experience, understanding the fundamentals of how something works is a great substitute to deploying an instrument in the field. I know I got a lot more of the former than the latter over the course of this internship, but I am leaving feeling very confident in my ability to perform technical duties aboard a scientific vessel. Again, I am very grateful to have had this opportunity, and I look forward to applying the skills I learned over the course of this internship to future projects.

Week 2 — Transit — Theo

2 weeks already—it’s a little hard to believe. We’ve been at sea for just about a week so far, and the transit has been great. We haven’t hit any patches of rough weather, and it’s starting to get a lot warmer too. The ocean has been choppy for most of the week, and the motion took some getting used to, but otherwise I’ve felt quite good this whole trip. Part of that is definitely because of our stewards; the food has honestly been amazing so far (to my surprise). One more week until Cape Verde!

Our biggest project since my last post has been our work on the digibirds. As a marine seismology vessel, the Langseth uses two key tools to gather seismic data while at sea. The first of these tools are our four airguns: sources that release soundwaves into the ocean that bounce off different layers of rock and sediment below the seafloor. The second of these tools are our streamers: four 15km long seismic hydrophone cables that float behind the research vessel listening for the returning soundwaves. Together, they allow researchers to gather 2D and 3D images of the ocean floor and the features beneath it. The digibirds themselves are devices that attach to the streamers that allow us to remotely monitor and control the position of the cables in the water column. Using the digibirds, we can keep the streamers at a specific depth and at a specific distance from one another, allowing us to gather more precise seismic data. The ones on the ship have been through a lot of wear and tear, so our job repairing them is critical for the ship’s ongoing research.

Over the course of this past week, Will and I have worked through about 60 digibirds. They’ve come with all sorts of issues: incorrect depth indicators, poor wing movement, broken motors, bad electrical systems, and even physical damage. For each bird, we’ve had to test thefunctionality of each system and identify what we can actually fix and what has to be sent back to LDEO. We calibrate the depth systems and test the movement of the wings, and if either of those fail we replace the wing module with one we know is functional. If either of those tests fail again, we know we have an issue with the bird itself, and not just the sensors. For the most part, however, we’ve been able to fix the birds up just by replacing or tweaking the wing module before recalibrating all systems. Definitely a cool hands-on mechanical and data-driven experience to have under my belt!

While that was definitely our biggest project this week, it wasn’t the only thing we did. One of our daily tasks at sea has been monitoring the echosounder and multibeam data streams and outputs. These are essentially the same device, except they output in 2D and 3D respectively, with the echosounder measuring the depth directly beneath the ship and the multibeam mapping underwater topography. We’ve learned how they function and how to read/analyze their data outputs, which will be super valuable for future projects. Other electronic systems we’ve worked on this week aboard the Langseth include installing a monitor displaying our sonar system power information, designing junction box schematics, and troubleshooting the AML SVP. This last device is used to measure the speed of sound in a given location and standardizes the measurements of our multibeam systems. It sits below the ship’s hull and has swappable attachments to measure temperature, salinity, pressure, and more. All in all, I’ve learned a lot this week, and I know there is much more to come!

 

Week 2 – Underway to Cape Verde – Will

Hello again from the R/V Langseth! This week has been very busy and productive as our responsibilities and tasks have increased since setting sail for Cape Verde 6 days ago! While the weather hasn’t been terrible the entire way, we have definitely hit a few rough patches here and there that have thrown me for a loop, but thankfully, I have started adjusting. Definitely bring some seasickness medication as a preventative!

We have certainly developed a greater understanding for the oceanographic equipment and seismic capability the Langseth is equipped with, as we have spent the majority of the week troubleshooting unique devices known as DigiBirds and monitoring the ship’s data streams. The Langseth is outfitted with 4-15km long streamers that deploy hydrophones into the water – these hydrophones are what makes the collection of seismic data and seafloor bathymetry possible! To adjust where in the water column the hydrophones “sit” and collect data, DigiBirds are placed along the hydrophone streamer ever 300 meters for a total of 52 DigiBirds when fully deployed! While these devices are highly versatile, allowing for the hydrophones to be adjusted within the water column from the comfort of the Langseth, they are just as susceptible to sensor drift and wear-and-tear as any other piece of oceanagraphic equipment.

Our primary responsibility this week was troubleshooting the various issues these DigiBirds had sustained over their last couple deployments, such as issues with their depth indicator, wings not adjusting properly, motor not functioning, or physical damage amongst a host of other miscellaneous problems. With each DigiBird, we would diagnose the issue and formulate the appropriate solution as to how we could return each bird to service. Some were easier than others, requiring a recalibration of their wings or depth indicator; however, some posed more complicated issues that we eventually learned to solve as our experience and confidence grew more and more. The birds that were beyond recovery (ie. physical damage) were labeled to be sent off back to Columbia. Over the course of the week, I believe we went through just about 60 of these devices! Not too shabby for our rookie debutes!

The other of our key responsibilites this week, and one that will continue until the conclusion of our time aboard the Langseth, was the monitoring of the Multibeam & Echosounder data collection, ensuring we were recieved an uninterupted stream of new, incoming data from our current cruise. These devices are responsible for the collection of 2D & 3D bathymetry mapping, allowing us to better understand the seafloor and add to a global database! In the above picture, you can see 2 sets of bathymetry data that are seperated by a black line. This is because the top portion of bathymetry data was from a previous cruise the Langseth took from Cape Verde while the bottom is the data we are currently taking and adding on to our database! The Chief Science Officer does his best to plot a route each cruise that allows the Langseth to maximize the amount of new bathymetry data it can collect.

We also had some fun today taking a photoshoot in full PPE “working” around the ship. The avid reader might notice I am working on the shelf that was fully constructed last week, anything for the LDEO LinkedIn! Some other minor tasks this week included inventorying our spare multibeam equipment, modifying the DigiBird storage in the A-Deck Lab to have dividers to increase organization, performing walkarounds to ensure all of our equipment is secure, and learning my bowline knot! Oh how I love my bowline knot. Thanks for reading, see you next week!

-Will

Week 1 — Preparing in Port — Theo

Hello! All is well on the Langseth; I’ve really enjoyed working with Cody (the Chief Science Officer), the other interns, and the rest of the crew so far. Quick update—we are no longer headed to Costa Rica. Things have been a little crazy around here, and because of some uncertainties about funding we’ve made a rare last minute change in plans. We are now headed to Cape Verde to pick up some OBS equipment that was deposited last year, which means we’re sailing across the Atlantic!

This first week has been super eventful and I’ve learned a lot. The Langseth is a very impressive boat and it’s been really great getting my bearings around the ship. It’s a global-class marine seismological vessel—the only of its kind in the UNOLS fleet—and the equipment they have on board is incredible. We’ll start working more closely with some of those systems next week—most of what we’ve done so far has involved a lot of maintenance and upkeep across the ship’s different labs and stations. We’ve packaged and shipped some outdated equipment back to Columbia and WHOI, and have also unpacked and stored new shipments of PPE, tools, and stores. Some daily and weekly responsibilities we have include cleaning the labs and making sure all loose items are tightly secured for the transit. It’s been quite busy but I’ve enjoyed getting my hands dirty, especially on a few key projects!

One of our first projects involved prepping the Lamont-Doherty Earth Observatory’s gravimeter for transport back to Columbia. This instrument is incredible—it’s a gray box built in the 60s that measures localized gravitational pull. It’s fragile and a little finicky, so we learned how to run daily checks on the instrumentation, run a gravity-tie test for calibration, and how to prepare it for transport without ruining everyone’s day (it would be a very costly break). We had to constantly keep it hooked up to a power supply and had to be very careful while moving it so as not to upset any of its internal workings. I’m very grateful I got the chance to work with it and to pick Cody’s brain about what makes it tick.

Another one of our projects was creating two shelfs/desks in the Dry Lab to create more workable surface area. I’ve never worked seriously with power tools before, and it was a blast getting to test things out with all the equipment and materials around the ship. This was definitely the project that took us the longest: we had to plan out the dimensions, clear the location, figure out our materials, cut out our metal frame, cut out our wooden surfaces, bolt pieces together, smooth out rough patches, and stain the wood. I’m very proud of our end product and it’ll definitely inspire me to work on more construction projects once I get home.

Finally, we spent some time on the workboat when we went to go get it fueled. This boat is kept on the ship in the event technicians need to perform maintenance on deployed equipment or lines. We were only supposed to be gone for an hour and a half, with the fuel dock being about 5 miles away, but our little vacation turned into a 4 hour maintenance trip. We initially had some problems with our electronics and port motor, which snowballed into an oil leak we had to patch and refill at the dock. It was a great time! We saw some dolphins, enjoyed the weather, and got very, very familiar with the inner workings of outboard motors.

Really looking forward to starting the transit tomorrow! I’m excited to get the ball rolling with a bit more technical projects, including working on our digibirds, getting familiar with our sonar systems, and testing out the streamers. Fingers crossed that I don’t get seasick!

Page 1 of 2

Powered by WordPress & Theme by Anders Norén