@misc{AcepclearskiesBuildClearSkiesmd, title = {Acep-Clear-Skies/Build/{{ClearSkies}}.Md at Main {$\cdot$} Acep-Uaf/Acep-Clear-Skies}, journal = {GitHub}, urldate = {2025-11-21}, abstract = {Contribute to acep-uaf/acep-clear-skies development by creating an account on GitHub.}, howpublished = {https://github.com/acep-uaf/acep-clear-skies/blob/main/build/ClearSkies.md}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/74GDLQQF/ClearSkies.html} } @misc{ACEPDataInventory, title = {{{ACEP Data Inventory Interface}}: {{Search ACEP}} Datasets by Title - {{Airtable}}}, urldate = {2025-11-21}, howpublished = {https://airtable.com/appGTI60XG5I3LB7w/pagYzFrgv9zKZr4YQ?Wt5gn=recyS2NXBolkzuGvz}, file = {/home/jehaverlack/Zotero/storage/HKI9RNU4/pagYzFrgv9zKZr4YQ.html} } @article{adamsSalamanderDiversityAbundance, title = {Salamander {{Diversity}} and {{Abundance Along Buck Run}} in {{The Laurel Fork Area}} of {{Highland County}}, {{Virginia}}}, author = {Adams, H Steve}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/DDS3PKUC/Adams - Salamander Diversity and Abundance Along Buck Run in The Laurel Fork Area of Highland County, Virgin.pdf} } @inproceedings{adamsTrustedCIExperiences2019, title = {Trusted {{CI Experiences}} in {{Cybersecurity}} and {{Service}} to {{Open Science}}}, booktitle = {Proceedings of the {{Practice}} and {{Experience}} in {{Advanced Research Computing}} on {{Rise}} of the {{Machines}} (Learning)}, author = {Adams, Andrew and Avila, Kay and Basney, Jim and Brunson, Dana and Cowles, Robert and Dopheide, Jeannette and Fleury, Terry and Heymann, Elisa and Hudson, Florence and Jackson, Craig and Kiser, Ryan and Krenz, Mark and Marsteller, Jim and Miller, Barton P. and Peisert, Sean and Russell, Scott and Sons, Susan and Welch, Von and Zage, John}, year = 2019, month = jul, pages = {1--8}, publisher = {ACM}, address = {Chicago IL USA}, doi = {10.1145/3332186.3340601}, urldate = {2026-01-22}, isbn = {978-1-4503-7227-5}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/K2HSHI6L/Adams et al. - 2019 - Trusted CI Experiences in Cybersecurity and Service to Open Science.pdf} } @misc{adediranWhatRailbelt2024, title = {What Is the {{Railbelt}}?}, author = {Adediran, Kemi}, year = 2024, month = aug, journal = {ArcGIS StoryMaps}, urldate = {2025-12-08}, abstract = {A overview of Alaska's energy structure and how it affects citizens of the 49th state}, howpublished = {https://storymaps.arcgis.com/stories/5311a23d5b7c46cdae3e622fb6961e14}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/58VIMEIN/5311a23d5b7c46cdae3e622fb6961e14.html} } @misc{AgeActuallyGood, title = {Age ({{Actually Good Encryption}})}, urldate = {2025-12-17}, howpublished = {https://asecuritysite.com/age/}, file = {/home/jehaverlack/Zotero/storage/HTAUXW3W/age.html} } @misc{AlaskaCenterEnergy, title = {The {{Alaska Center}} for {{Energy}} and {{Power}} ({{ACEP}}) \textbar{} {{ACEP}}}, urldate = {2025-11-07}, howpublished = {https://acep.uaf.edu/}, file = {/home/jehaverlack/Zotero/storage/4YG93UK9/acep.html} } @misc{AlaskaCenterEnergya, title = {The {{Alaska Center}} for {{Energy}} and {{Power}} ({{ACEP}}) \textbar{} {{ACEP}}}, urldate = {2025-11-22}, howpublished = {https://www.uaf.edu/acep/}, file = {/home/jehaverlack/Zotero/storage/4Y954A8I/acep.html} } @misc{AlaskaRailbeltReliability2025, title = {Alaska {{Railbelt Reliability Council}}}, year = 2025, month = nov, journal = {RRC Local}, urldate = {2025-11-07}, abstract = {Alaska Railbelt Reliability Council RRC}, howpublished = {https://www.akrrc.org/}, langid = {english} } @misc{AlaskaRuralEnergy, title = {Alaska {{Rural Energy Conference}}}, journal = {Alaska Rural Energy Conference}, urldate = {2025-12-08}, abstract = {Join communities and experts on October 2-4, 2024 in Fairbanks to discuss energy projects, ideas, and solutions for rural Alaska.}, howpublished = {https://akruralenergy.org/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/8D7LMAS2/akruralenergy.org.html} } @misc{AlaskaRuralEnergya, title = {Alaska {{Rural Energy Conference}}}, urldate = {2025-12-09}, howpublished = {https://akruralenergy.org/} } @misc{AlaskaRuralEnergyb, title = {Alaska {{Rural Energy Conference}}}, journal = {Alaska Rural Energy Conference}, urldate = {2025-12-09}, abstract = {Join communities and experts on October 2-4, 2024 in Fairbanks to discuss energy projects, ideas, and solutions for rural Alaska.}, howpublished = {https://akruralenergy.org/}, langid = {american} } @misc{AlaskaSustainableEnergy, title = {Alaska {{Sustainable Energy Conference}} \textbar{} {{Alaska Sustainable Energy Conference}}}, urldate = {2025-12-08}, howpublished = {https://alaskasustainableenergy.com/}, file = {/home/jehaverlack/Zotero/storage/ET34U4WI/alaskasustainableenergy.com.html} } @misc{AlaskaSustainableEnergya, title = {Alaska {{Sustainable Energy Conference}} \textbar{} {{Alaska Sustainable Energy Conference}}}, urldate = {2025-12-09}, howpublished = {https://alaskasustainableenergy.com/} } @misc{AllenBradleyProductsAllenBradley, title = {Allen-{{Bradley Products}} \textbar{} {{Allen-Bradley}} \textbar{} {{US}}}, urldate = {2025-11-21}, howpublished = {https://www.rockwellautomation.com/en-us/products/hardware/allen-bradley.html}, file = {/home/jehaverlack/Zotero/storage/8PJKVGXM/allen-bradley.html} } @misc{AmazoncomCaseReality, title = {Amazon.Com: {{The Case Against Reality}}: {{Why Evolution Hid}} the {{Truth}} from {{Our Eyes}}: 9780393254693: {{Hoffman}}, {{Donald}}: {{Books}}}, urldate = {2025-11-07}, howpublished = {https://www.amazon.com/Case-Against-Reality-Evolution-Truth/dp/0393254690}, file = {/home/jehaverlack/Zotero/storage/UZ85T5AH/0393254690.html} } @misc{Ameliorated, title = {Ameliorated}, urldate = {2025-11-05}, abstract = {Completely transform your computer in minutes. Simply download a verified Playbook, or use your own, and run it in AME Beta.}, howpublished = {https://amelabs.net/}, langid = {english} } @misc{AppOmniLabsHeisenbergsschealthcheck2025, title = {{{AppOmni-Labs}}/Heisenberg-Ssc-Health-Check}, year = 2025, month = nov, urldate = {2025-11-03}, abstract = {Analyzes software dependencies across GitHub repositories to identify security vulnerabilities and health risks in your supply chain.}, copyright = {MIT}, howpublished = {AppOmni Labs} } @article{ArtificialIntelligence2017, title = {Artificial Intelligence}, year = 2017, month = jun, journal = {NIST}, urldate = {2025-11-07}, abstract = {NIST promotes innovation and cultivates trust in the design, development, use and governance of artificial intelligen}, langid = {english}, annotation = {Last Modified: 2025-09-04T08:20-04:00} } @misc{ASLLinuxCompatible, title = {{{ASL}} - {{Linux}} Compatible Servers, Workstations and Storage}, urldate = {2025-11-07}, howpublished = {https://www.aslab.com/}, file = {/home/jehaverlack/Zotero/storage/HZKWTGLG/www.aslab.com.html} } @misc{ASSISTQuickSearchDocumentDetails, title = {{{ASSIST-QuickSearch Document Details}}}, urldate = {2025-12-01}, howpublished = {https://quicksearch.dla.mil/qsDocDetails.aspx?ident\_number=285095}, file = {/home/jehaverlack/Zotero/storage/I4WDU5KP/qsDocDetails.html} } @misc{ASSISTQuickSearchMILSTD3071, title = {{{ASSIST-QuickSearch MIL-STD-3071}}}, urldate = {2025-12-01}, howpublished = {https://quicksearch.dla.mil/qsDocDetails.aspx?ident\_number=285095}, file = {/home/jehaverlack/Zotero/storage/52S9FHKB/qsDocDetails.html} } @misc{AtlasOSAtlas2025, title = {Atlas-{{OS}}/{{Atlas}}}, year = 2025, month = nov, urldate = {2025-11-05}, abstract = {🚀 An open and lightweight modification to Windows, designed to optimize performance, privacy and usability.}, copyright = {GPL-3.0}, howpublished = {Atlas}, keywords = {ame-wizard,atlas,atlasos,debloat,fps,gaming,latency,open-source,opensource,performance,privacy,security,tweaks,windows} } @misc{authorsHeadscale, title = {Headscale}, author = {{authors}, Headscale}, urldate = {2025-11-07}, abstract = {An open source, self-hosted implementation of the Tailscale control server.}, howpublished = {https://juanfont.github.io/headscale/0.27.0/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/IA7TPZR3/0.27.0.html} } @article{Availability2025, title = {Availability}, year = 2025, month = aug, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {In reliability engineering, the term availability has the following meanings: The degree to which a system, subsystem or equipment is in a specified operable and committable state at the start of a mission, when the mission is called for at an unknown, i.e. a random, time. The probability that an item will operate satisfactorily at a given point in time when used under stated conditions in an ideal support environment. Normally high availability systems might be specified as 99.98\%, 99.999\% or 99.9996\%. The converse, unavailability, is 1 minus the availability.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1303680427}, file = {/home/jehaverlack/Zotero/storage/WXU7YTT8/index.html} } @misc{BackdoorsBreaches, title = {Backdoors \& {{Breaches}}}, journal = {Black Hills Information Security, Inc.}, urldate = {2026-01-20}, abstract = {Backdoors \& Breaches Backdoors \& Breaches is the original cooperative incident response card game fromBlack Hills Information Security and Active Countermeasures.The Core Deck contains 52 unique cards that help teams [\dots ]}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/LNYUF82B/backdoorsandbreaches.html} } @misc{BipartisanInfrastructureLaw, title = {Bipartisan {{Infrastructure Law Implementation}}}, journal = {Energy.gov}, urldate = {2025-11-07}, abstract = {Congress has provided DOE \$27 billion to upgrade and modernize our electrical grid to make it more resilient to extreme weather and resistant to cyber-attacks, helping CESER advance its energy security mission.}, howpublished = {https://www.energy.gov/ceser/bipartisan-infrastructure-law-implementation}, langid = {english} } @article{bohnOverviewMILSTD3071Tactical, title = {Overview of {{MIL-STD-3071}} -- {{Tactical Microgrid Standard}}}, author = {Bohn, Frank W}, abstract = {MIL-STD-3071, or the Tactical Microgrid Standard (TMS), is a data and communication standard for power devices to maximize interoperability between power solutions from various vendors. The TMS implements a data model for each type of power device that allows participants on the microgrid to know the type of device and associated capabilities. TMS also implements the role of Microgrid Controllers (MC) and Microgrid Dashboard (MD). The MC collects the real time data from the various power devices and acts as a supervisory controller to optimize the power devices in terms of fuel efficiency or resiliency. The MD provides the ability to display all the real time data to the user in one location.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/QHCTU65Z/Bohn - Overview of MIL-STD-3071 – Tactical Microgrid Standard.pdf} } @misc{bryopsidaBryopsidaNodefips2026, title = {Bryopsida/Node-Fips}, author = {{bryopsida}}, year = 2026, month = jan, urldate = {2026-01-08}, abstract = {A Node.JS LTS image with OpenSSL FIPS provider included and FIPS enabled by default in Node Crypto}, keywords = {docker-image,fips,multi-platform,nodejs,openssl-fips} } @misc{C2M2, title = {{{C2M2}}}, urldate = {2025-11-07}, howpublished = {https://c2m2.doe.gov/}, file = {/home/jehaverlack/Zotero/storage/TCXVKQSV/c2m2.doe.gov.html} } @misc{ChirpStackOpensourceLoRaWAN, title = {{{ChirpStack}} Open-Source {{LoRaWAN Network Server}}}, urldate = {2026-01-13}, howpublished = {https://www.chirpstack.io/}, file = {/home/jehaverlack/Zotero/storage/526B7F2J/www.chirpstack.io.html} } @misc{CIPCriticalInfrastructure2025, title = {({{CIP}}) {{Critical Infrastructure Protection}}}, year = 2025, month = nov, journal = {RRC Local}, urldate = {2025-11-07}, abstract = {Alaska's first Electric Reliability Organization}, howpublished = {https://www.akrrc.org/matters/category/cip-critical-infrastructure-protection}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/U8E4M4FC/cip-critical-infrastructure-protection.html} } @misc{CISControls, title = {{{CIS Controls}}}, journal = {CIS}, urldate = {2025-11-07}, abstract = {The Center for Internet Security (CIS) officially launched CIS Controls v8, which was enhanced to keep up with evolving technology now including cloud and mobile technologies.}, howpublished = {https://www.cisecurity.org/controls/}, langid = {english} } @article{CMMCAssessmentGuide, title = {{{CMMC Assessment Guide Level}} 1}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/JA96FUSH/CMMC Assessment Guide Level 1.pdf} } @article{CMMCAssessmentGuidea, title = {{{CMMC Assessment Guide Level}} 2}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/6YV3HDT7/CMMC Assessment Guide Level 2.pdf} } @article{CMMCAssessmentGuideb, title = {{{CMMC Assessment Guide Level}} 3}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/4I3HQ5VZ/CMMC Assessment Guide Level 3.pdf} } @article{CMMCModelOverview, title = {{{CMMC Model Overview Version}} 2.13}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/DZKQCELK/CMMC Model Overview Version 2.13.pdf} } @article{CMMCScopingGuide, title = {{{CMMC Scoping Guide Level}} 1}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/5VSEREX8/CMMC Scoping Guide Level 1.pdf} } @article{CMMCScopingGuidea, title = {{{CMMC Scoping Guide Level}} 2}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/5WYZXWKT/CMMC Scoping Guide Level 2.pdf} } @techreport{committeeGuidelinesSmartGrid2014, title = {Guidelines for {{Smart Grid Cybersecurity}}}, author = {Committee, The Smart Grid Interoperability Panel-Smart Grid Cybersecurity}, year = 2014, month = sep, number = {NIST Internal or Interagency Report (NISTIR) 7628 Rev. 1}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.IR.7628r1}, urldate = {2025-11-07}, abstract = {This three-volume report, Guidelines for Smart Grid Cybersecurity, presents an analytical framework that organizations can use to develop effective cybersecurity strategies tailored to their particular combinations of Smart Grid-related characteristics, risks, and vulnerabilities. Organizations in the diverse community of Smart Grid stakeholders---from utilities to providers of energy management services to manufacturers of electric vehicles and charging stations---can use the methods and supporting information presented in this report as guidance for assessing risk and identifying and applying appropriate security requirements. This approach recognizes that the electric grid is changing from a relatively closed system to a complex, highly interconnected environment. Each organization's cybersecurity requirements should evolve as technology advances and as threats to grid security inevitably multiply and diversify.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/2DWPQZM5/Committee - 2014 - Guidelines for Smart Grid Cybersecurity.pdf} } @misc{computersecuritydivisionInformativeReferenceDetails2020, title = {Informative {{Reference Details}} - {{National Online Informative References Program}} \textbar{} {{CSRC}} \textbar{} {{CSRC}}}, author = {Computer Security Division, Information Technology Laboratory}, year = 2020, month = sep, journal = {CSRC \textbar{} NIST}, urldate = {2025-12-08}, howpublished = {https://csrc.nist.gov/projects/olir/informative-reference-catalog/details}, langid = {american} } @misc{CoopCyberGoals2022, title = {Co-Op {{Cyber Goals Program}}}, year = {2022-12-15T11:22:5+00:00}, journal = {Cooperative.com}, urldate = {2026-01-20}, abstract = {Providing electric cooperatives with actionable guidance on ways to advance their cybersecurity posture.}, howpublished = {https://www.cooperative.com/programs-services/bts/rc3/cyber-goals/Pages/default.aspx}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/2GSA3HGB/default.html} } @misc{CoursesGRCAcademy, title = {Courses - {{GRC Academy}}}, urldate = {2025-11-21}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/ZJ76WLBL/courses.html} } @article{CriticalInfrastructure2025, title = {Critical Infrastructure}, year = 2025, month = oct, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Critical infrastructure, or critical national infrastructure (CNI) in the UK, describes infrastructure considered essential by governments for the functioning of a society and economy and deserving of special protection for national security. Critical infrastructure has traditionally been viewed as under the scope of government due to its strategic importance, yet there is an observable trend towards its privatization, raising discussions about how the private sector can contribute to these essential services.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1316156920}, file = {/home/jehaverlack/Zotero/storage/92LHRRUM/index.html} } @misc{CriticalInfrastructureSectors, title = {Critical {{Infrastructure Sectors}} \textbar{} {{CISA}}}, urldate = {2025-11-07}, howpublished = {https://www.cisa.gov/topics/critical-infrastructure-security-and-resilience/critical-infrastructure-sectors}, langid = {english} } @article{CSF11Archive2018, title = {{{CSF}} 1.1 {{Archive}}}, year = 2018, month = feb, journal = {NIST}, urldate = {2025-11-07}, langid = {english}, annotation = {Last Modified: 2024-02-26T09:11-05:00} } @misc{CyberChef, title = {{{CyberChef}}}, urldate = {2025-11-21}, howpublished = {https://cyberchef.org/}, file = {/home/jehaverlack/Zotero/storage/ZGQ3BMAG/cyberchef.org.html} } @misc{CyberphysicalAdvancedMetering, title = {Cyberphysical {{Advanced Metering Infrastructure}} for {{IT-OT}} Laboratory ({{CAMIO}})}, journal = {CAMIO}, urldate = {2025-12-01}, abstract = {Public Docs for CAMIO: Cyberphysical Advanced Metering Infrastructure for IT-OT laboratory}, howpublished = {https://acep-uaf.github.io/CAMIO/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/UDZJUZQF/CAMIO.html} } @misc{CybersecurityAmbassadorProgram, title = {Cybersecurity {{Ambassador Program}} -- {{Department}} of {{Technology}}}, urldate = {2026-01-14}, howpublished = {https://usm.maine.edu/department-technology/cybersecurity-ambassador-program/}, file = {/home/jehaverlack/Zotero/storage/K49SFZSM/cybersecurity-ambassador-program.html} } @misc{CybersecurityCapabilityMaturity, title = {Cybersecurity {{Capability Maturity Model}} ({{C2M2}})}, journal = {Energy.gov}, urldate = {2025-11-07}, abstract = {The Cybersecurity Capability Maturity Model (C2M2) is a free tool to help organizations evaluate their cybersecurity capabilities and optimize security investments.}, howpublished = {https://www.energy.gov/ceser/cybersecurity-capability-maturity-model-c2m2}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/B3GFZAVM/cybersecurity-capability-maturity-model-c2m2.html} } @misc{DataSharingAgreements, title = {Data {{Sharing Agreements}} from {{AirTable}} Inventory - {{Google Sheets}}}, urldate = {2025-11-21}, howpublished = {https://docs.google.com/spreadsheets/d/12wx6fPja3\_7fuQ-EOSlkXekC7f1dMkptYY168E0-yrA/edit?gid=854937934\#gid=854937934}, file = {/home/jehaverlack/Zotero/storage/ELBF7MZI/edit.html} } @misc{DeepMachineLearning, title = {Deep {{Machine Learning}} for {{Intrusion Detection}} in {{Cyber-Physical Critical Infrastructures}}.Pdf}, journal = {Google Docs}, urldate = {2025-12-17}, howpublished = {https://drive.google.com/file/d/1jU0pIHpAOjk\_1e4COwZwn5ilcNISxo1Y/view?usp=embed\_facebook}, file = {/home/jehaverlack/Zotero/storage/A3Q9X68R/view.html} } @misc{DepartmentEnergysCyberForce, title = {Department of {{Energy}}'s {{CyberForce}}\textregistered{} {{Program}}}, urldate = {2026-01-14}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/R68UMHEQ/cyberforce.energy.gov.html} } @misc{DeployHyperConvergedCeph, title = {Deploy {{Hyper-Converged Ceph Cluster}} - {{Proxmox VE}}}, urldate = {2025-11-13}, howpublished = {https://pve.proxmox.com/wiki/Deploy\_Hyper-Converged\_Ceph\_Cluster}, file = {/home/jehaverlack/Zotero/storage/RKWNF629/Deploy_Hyper-Converged_Ceph_Cluster.html} } @misc{DigitizingUtilitiesPrize, title = {Digitizing {{Utilities Prize Round}} 3: {{Resilient Grid Innovation}} \textbar{} {{HeroX}}}, shorttitle = {Digitizing {{Utilities Prize Round}} 3}, urldate = {2026-01-12}, abstract = {Help electric utilities facilitate the transformation of digital systems, data analytics, and risk-informed resource integration}, howpublished = {https://www.herox.com/DigitizingUtilitiesPrizeRound3}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/JRB6G88E/DigitizingUtilitiesPrizeRound3.html} } @misc{DragosCybersecurityCommunity, title = {Dragos {{Cybersecurity Community Resources}}}, urldate = {2025-11-07}, abstract = {Furthering our mission to help build a community to secure industrial control systems (ICS) and operational technology (OT) from cyber threats.}, howpublished = {https://www.dragos.com/community}, langid = {american} } @article{duncanDODCybersecuritySAP, title = {{{DOD Cybersecurity}} \& {{SAP IT Summit}}}, author = {Duncan, John}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/7F6NVMMF/Duncan - DOD Cybersecurity & SAP IT Summit.pdf} } @article{FaultTolerance2025, title = {Fault Tolerance}, year = 2025, month = oct, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Fault tolerance is the ability of a system to maintain proper operation despite failures or faults in one or more of its components. This capability is essential for high-availability, mission-critical, or even life-critical systems. Fault tolerance specifically refers to a system's capability to handle faults without any degradation or downtime. In the event of an error, end-users remain unaware of any issues. Conversely, a system that experiences errors with some interruption in service or graceful degradation of performance is termed 'resilient'. In resilience, the system adapts to the error, maintaining service but acknowledging a certain impact on performance. Typically, fault tolerance describes computer systems, ensuring the overall system remains functional despite hardware or software issues. Non-computing examples include structures that retain their integrity despite damage from fatigue, corrosion or impact.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1318420800}, file = {/home/jehaverlack/Zotero/storage/X6I4ALKB/index.html} } @misc{FindRaspberryPi, title = {Find {{Raspberry Pi}} Computers in Stock}, journal = {rpilocator}, urldate = {2025-11-05}, abstract = {Find Raspberry Pi computers in stock - rpilocator}, howpublished = {https://rpilocator.com/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/R2LZP397/rpilocator.com.html} } @misc{Firecracker, title = {Firecracker}, urldate = {2025-11-20}, howpublished = {https://firecracker-microvm.github.io/}, file = {/home/jehaverlack/Zotero/storage/EFVMVQ7P/firecracker-microvm.github.io.html} } @misc{FiveICSCybersecurity, title = {The {{Five ICS Cybersecurity Critical Controls}}}, journal = {SANS Institute}, urldate = {2025-12-08}, abstract = {This paper sets forth the five most relevant critical controls for an ICS/OT cybersecurity strategy...}, howpublished = {https://www.sans.org/white-papers/five-ics-cybersecurity-critical-controls}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/CT55ACNK/five-ics-cybersecurity-critical-controls.html} } @misc{FrameworkCore, title = {Framework {{Core}}}, journal = {Trusted CI: The NSF Cybersecurity Center of Excellence}, urldate = {2025-11-07}, howpublished = {https://www.trustedci.org/framework/core}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/X4AN87M4/core.html} } @misc{Gallery, title = {Gallery}, journal = {Quarto}, urldate = {2025-11-07}, abstract = {A gallery of example documents, websites, books, and presentations created with Quarto.}, howpublished = {https://quarto.org/docs/gallery/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/NSPYJH6C/gallery.html} } @misc{gianfortunePentagonsCMMCDeadline2025, title = {Pentagon's {{CMMC Deadline Arrives Amid Government Shutdown}}}, author = {Gianfortune, Ross}, year = 2025, month = nov, journal = {GovCIO Media \& Research}, urldate = {2025-12-04}, abstract = {The Pentagon will enforce new cybersecurity requirements across the defense supply chain amid a federal shutdown.}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/QUDVBXXJ/pentagons-cmmc-deadline-arrives-amid-government-shutdown.html} } @misc{GMLC1321Alaska, title = {{{GMLC}} 1.3.21 - {{Alaska Microgrid Partnership}}}, journal = {Energy.gov}, urldate = {2025-12-08}, abstract = {Lead Performer: National Renewable Energy Laboratory -- Golden, CO}, howpublished = {https://www.energy.gov/eere/buildings/articles/gmlc-1321-alaska-microgrid-partnership}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/7THYCL2X/gmlc-1321-alaska-microgrid-partnership.html} } @misc{heynsRetorquereZoterodeb2025, title = {Retorquere/Zotero-Deb}, author = {Heyns, Emiliano}, year = 2025, month = sep, urldate = {2025-09-30}, abstract = {Packaged versions of Zotero and Juris-M for Debian-based systems}, copyright = {MIT} } @article{HighAvailability2025, title = {High Availability}, year = 2025, month = aug, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {High availability (HA) is a characteristic of a system that aims to ensure an agreed level of operational performance, usually uptime, for a higher than normal period. There is now more dependence on these systems as a result of modernization. For example, to carry out their regular daily tasks, hospitals and data centers need their systems to be highly available. Availability refers to the ability of the user to access a service or system, whether to submit new work, update or modify existing work, or retrieve the results of previous work. If a user cannot access the system, it is considered unavailable from the user's perspective. The term downtime is generally used to refer to describe periods when a system is unavailable.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1307901527}, file = {/home/jehaverlack/Zotero/storage/GEP7QMIY/index.html} } @misc{HomeCyberFramework, title = {Home \textbar{} {{DER Cyber Framework}} \textbar{} {{NLR}}}, urldate = {2026-01-20}, howpublished = {https://dercf.nrel.gov/}, file = {/home/jehaverlack/Zotero/storage/KRHDPED7/dercf.nrel.gov.html} } @misc{HomePageFederal, title = {Home {{Page}} \textbar{} {{Federal Energy Regulatory Commission}}}, urldate = {2025-11-07}, howpublished = {https://www.ferc.gov/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/MABSEF33/www.ferc.gov.html} } @misc{HomePageFederala, title = {Home {{Page}} \textbar{} {{Federal Energy Regulatory Commission}}}, urldate = {2025-12-08}, howpublished = {https://www.ferc.gov/}, langid = {english} } @misc{hughesBeaufortSeaIce, title = {Beaufort {{Sea}} Ice Cuts Fiber-Optic Cable, Limiting Internet for about 20,000 Residents of {{Northwest Alaska}} through Summer}, author = {Hughes, Zachariah}, journal = {Anchorage Daily News}, urldate = {2026-01-20}, abstract = {The subsea cable is owned by Quintillion but affects companies delivering internet access to residents, schools and local governments.}, chapter = {Rural Alaska, Business/Economy, Alaska News}, howpublished = {https://www.adn.com/alaska-news/rural-alaska/2025/02/04/beaufort-sea-ice-snips-fiber-optic-cable-limiting-internet-for-some-20000-in-northwest-alaska-until-after-summer/}, file = {/home/jehaverlack/Zotero/storage/QJR7YMZ3/beaufort-sea-ice-snips-fiber-optic-cable-limiting-internet-for-some-20000-in-northwest-alaska-u.html} } @misc{HuskyHackersDepartment, title = {Husky {{Hackers}} -- {{Department}} of {{Technology}}}, urldate = {2026-01-14}, howpublished = {https://usm.maine.edu/department-technology/husky-hackers-2/}, file = {/home/jehaverlack/Zotero/storage/9RSAP8Q7/husky-hackers-2.html} } @misc{IndexDebiancdCurrent, title = {Index of /Debian-Cd/Current/Amd64}, urldate = {2026-01-06}, howpublished = {https://cdimage.debian.org/debian-cd/current/amd64/}, file = {/home/jehaverlack/Zotero/storage/54DW85CP/amd64.html} } @misc{ISC2CodeEthics, title = {{{ISC2 Code}} of {{Ethics}}---{{Guidance}} for {{Cybersecurity Professionals}}}, urldate = {2026-02-04}, abstract = {The safety and welfare of society and the common good, duty to our principles, and duty to each other, requires that we adhere, and be seen to adhere, to the highest ethical standards of behavior.}, howpublished = {https://www.isc2.org/ethics}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/24YIC436/ethics.html} } @misc{ItkSourceLorhammer2025, title = {{{itkSource}}/Lorhammer}, year = 2025, month = sep, urldate = {2026-01-13}, abstract = {Stress your lora network-server - mirror of https://gitlab.com/itk.fr/lorhammer}, howpublished = {itkSource}, keywords = {distributed,golang,lorawan,stress-testing} } @misc{JehaverlackBasicbookbuilderPandoc, title = {Jehaverlack/Basic-Book-Builder: {{A Pandoc}} Workflow for Building {{PDF}}, {{HTML}}, {{EPUB}}, and {{LaTeX}} Book Format.}, urldate = {2025-11-13}, howpublished = {https://github.com/jehaverlack/basic-book-builder/tree/main}, file = {/home/jehaverlack/Zotero/storage/YW57X4FT/main.html} } @misc{JohnHaverlackACEP, title = {John {{Haverlack}} \textbar{} {{ACEP}}}, urldate = {2025-09-30}, howpublished = {https://www.uaf.edu/acep/about/our-team/john-haverlack.php}, file = {/home/jehaverlack/Zotero/storage/ZJEZWUFM/john-haverlack.html} } @article{KesslerSyndrome2025, title = {Kessler Syndrome}, year = 2025, month = oct, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {The Kessler syndrome, also known as the Kessler effect, collisional cascading, or ablation cascade, is a scenario proposed by NASA scientists Donald J. Kessler and Burton G. Cour-Palais in 1978. It describes a situation in which the density of objects in low Earth orbit (LEO) becomes so high due to space pollution that collisions between these objects cascade, exponentially increasing the amount of space debris over time. This proliferation of debris poses significant risks to satellites, space missions, and the International Space Station, potentially rendering certain orbital regions unusable and threatening the sustainability of space activities for many generations. In 2009, Kessler wrote that modeling results indicated the debris environment had already become unstable, meaning that efforts to achieve a growth-free small debris environment by eliminating past debris sources would likely fail because fragments from future collisions would accumulate faster than atmospheric drag could remove them. The Kessler syndrome underscores the critical need for effective space traffic management and collision avoidance strategies to ensure the long-term viability of space exploration and utilization.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1318711076}, file = {/home/jehaverlack/Zotero/storage/7AG3T8XL/index.html} } @misc{knightCutCableCauses2023, title = {Cut Cable Causes Internet and Cellphone Outages in {{Arctic Alaska}}}, author = {Knight, Greg}, year = 2023, month = jun, journal = {Alaska Public Media}, urldate = {2026-01-20}, abstract = {Quintillion President Mike McHale said a full restoration of internet and some cellphone service could take up to two months.}, chapter = {Latest News}, howpublished = {https://alaskapublic.org/news/2023-06-12/cut-cable-causes-weeks-long-north-slope-northwest-alaska-internet-and-cellphone-outages}, langid = {english} } @article{LoRa2025, title = {{{LoRa}}}, year = 2025, month = nov, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {LoRa (from "long range") is a physical proprietary radio communication technique based on spread spectrum modulation. It is used as the physical layer for LoRaWAN, a low-power, wide-area network (LPWAN) protocol that wirelessly connects battery-operated devices to the Internet. LoRa can be thought of as the radio signal technology (similar to Wi-Fi or cellular), while LoRaWAN is the protocol and network architecture that manages communication over that signal. Together, LoRa and LoRaWAN provide a solution for connecting low-power devices over long distances, making them a key technology for the Internet of Things (IoT). The technology is primarily used for applications where small amounts of data need to be transmitted infrequently from hard-to-reach locations, such as in smart agriculture, industrial monitoring, and asset tracking. The technology was originally developed by the French company Cycleo, which was acquired by Semtech in 2012, and the LoRaWAN standard is now managed by the LoRa Alliance.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1319982564}, file = {/home/jehaverlack/Zotero/storage/P53WAJJ4/index.html} } @article{LoRa2025a, title = {{{LoRa}}}, year = 2025, month = dec, journal = {Wikipedia}, urldate = {2026-01-20}, abstract = {LoRa (from "long range") is a physical proprietary radio communication technique based on spread spectrum modulation. It is used as the physical layer for LoRaWAN, a low-power, wide-area network (LPWAN) protocol that wirelessly connects battery-operated devices to the Internet. LoRa can be thought of as the radio signal technology (similar to Wi-Fi or cellular), while LoRaWAN is the protocol and network architecture that manages communication over that signal. Together, LoRa and LoRaWAN provide a solution for connecting low-power devices over long distances, making them a key technology for the Internet of Things (IoT). The technology is primarily used for applications where small amounts of data need to be transmitted infrequently from hard-to-reach locations, such as in smart agriculture, industrial monitoring, and asset tracking. The technology was originally developed by the French company Cycleo, which was acquired by Semtech in 2012, and the LoRaWAN standard is now managed by the LoRa Alliance.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1326721587}, file = {/home/jehaverlack/Zotero/storage/PRC6QZW3/index.html} } @misc{LoRaWANArchitecture, title = {{{LoRaWAN Architecture}}}, journal = {The Things Network}, urldate = {2026-01-20}, abstract = {We are building a global open free crowdsourced long range low power IoT data network}, howpublished = {https://www.thethingsnetwork.org/docs/lorawan/architecture/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/2PDIW4BV/architecture.html} } @misc{LoRaWANVersionsRevisions, title = {{{LoRaWAN}}: Versions and Revisions}, shorttitle = {{{LoRaWAN}}}, journal = {GitHub}, urldate = {2026-01-20}, abstract = {Universal wireless communication library for embedded devices - jgromes/RadioLib}, howpublished = {https://github.com/jgromes/RadioLib/wiki/LoRaWAN:-versions-and-revisions}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/9IQLPGX2/LoRaWAN-versions-and-revisions.html} } @article{LowEarthOrbit2025, title = {Low {{Earth}} Orbit}, year = 2025, month = oct, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {A low Earth orbit (LEO) is an orbit around Earth with a period of 128 minutes or less (making at least 11.25 orbits per day) and an eccentricity less than 0.25. Most of the artificial objects in outer space are in LEO, peaking in number at an altitude around 800 km (500 mi), while the farthest in LEO, before medium Earth orbit (MEO), have an altitude of 2,000 kilometers, about one-third of the radius of Earth and near the beginning of the inner Van Allen radiation belt. The term LEO region is used for the area of space below an altitude of 2,000 km (1,200 mi) (about one-third of Earth's radius). Objects in orbits that pass through this zone, even if they have an apogee further out or are sub-orbital, are carefully tracked since they present a collision risk to the many LEO satellites. No human spaceflights other than the lunar missions of the Apollo program (1968--1972) have gone beyond LEO. Artemis II is also planned to go beyond LEO in early 2026. All space stations to date have operated geocentric within LEO.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1317788287}, file = {/home/jehaverlack/Zotero/storage/PNC5KFJM/index.html} } @misc{Malcolm, title = {Malcolm}, journal = {Malcolm}, urldate = {2025-09-30}, abstract = {A powerful, easily deployable network traffic analysis tool suite for network security monitoring}, howpublished = {https://malcolm.fyi/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/VFJARZP4/malcolm.fyi.html} } @misc{MiniPCsMini, title = {Mini {{PCs}} \textbar{} {{Mini Work Station}} \textbar{} {{Tablets}} \textbar{} {{Minisforum}}}, urldate = {2025-11-07}, howpublished = {https://store.minisforum.com/?utm\_medium=cpc}, file = {/home/jehaverlack/Zotero/storage/2VN5ZDCR/store.minisforum.com.html} } @misc{MooseFS, title = {{{MooseFS}}}, journal = {MooseFS Distributed Storage -- the best Open Source Distributed File System / Software-Defined Storage}, urldate = {2025-12-02}, abstract = {The Best Open-Source Distributed Filesystem}, howpublished = {https://moosefs.com}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/4D5BYVQ9/moosefs.com.html} } @misc{MQTTSparkplugVs2025, title = {{{MQTT Sparkplug}} vs. {{Plain MQTT}}: {{Why Sparkplug Matters}} for {{IIoT}}}, shorttitle = {{{MQTT Sparkplug}} vs. {{Plain MQTT}}}, year = 2025, month = mar, journal = {Ubidots Blog}, urldate = {2026-01-22}, abstract = {MQTT Sparkplug simplifies IIoT with structured data, real-time device state awareness, and seamless scalability for industrial networks.}, howpublished = {https://ubidots.com/blog/mqtt-sparkplug-vs-plain-mqtt/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/37C7CJ3U/mqtt-sparkplug-vs-plain-mqtt.html} } @misc{NationalCyberLeague, title = {National {{Cyber League Webpage}}}, journal = {National Cyber League Webpage}, urldate = {2026-01-14}, abstract = {The NCL is a learning-centered cybersecurity competition and community for high school and college students.}, howpublished = {https://nationalcyberleague.org}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/8Q8QY9KD/nationalcyberleague.org.html} } @misc{NCCDCHome, title = {{{NCCDC}} - {{Home}}}, urldate = {2026-01-14}, howpublished = {https://www.nationalccdc.org/}, file = {/home/jehaverlack/Zotero/storage/XPV3XQ34/www.nationalccdc.org.html} } @misc{NERC, title = {{{NERC}}}, urldate = {2025-11-07}, howpublished = {https://www.nerc.com/Pages/default.aspx}, file = {/home/jehaverlack/Zotero/storage/4HU3ES6I/default.html} } @article{NICEFrameworkResource2019, title = {{{NICE Framework Resource Center}}}, year = 2019, month = nov, journal = {NIST}, urldate = {2026-01-14}, abstract = {The NICE Framework establishes a common language that describes cybersecurity work and the knowledge and skills needed to complete that work. It is used in public and private sectors and across industries for career discovery, education and training, and in hiring and workforce development.}, langid = {english}, annotation = {Last Modified: 2025-12-19T15:56-05:00}, file = {/home/jehaverlack/Zotero/storage/XW9QKDJN/nice-framework-resource-center.html} } @misc{NSF25543Computer, title = {{{NSF}} 25-543: {{Computer}} and {{Information Science}} and {{Engineering}} : {{Future Computing Research}} ({{Future CoRe}}) \textbar{} {{NSF}} - {{U}}.{{S}}. {{National Science Foundation}}}, shorttitle = {{{NSF}} 25-543}, urldate = {2025-12-17}, howpublished = {https://www.nsf.gov/funding/opportunities/future-core-computer-information-science-engineering-future-computing/nsf25-543/solicitation}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/8GNZNXMQ/solicitation.html} } @misc{NSFProposalAward, title = {{{NSF Proposal}} \& {{Award Policies}} \& {{Procedures Guide}} ({{PAPPG}}) \textbar{} {{NSF}} - {{U}}.{{S}}. {{National Science Foundation}}}, urldate = {2026-01-14}, howpublished = {https://www.nsf.gov/policies/pappg}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/95HF82AL/pappg.html} } @misc{o&osoftwareOOShutUp10Free, title = {O\&{{O ShutUp10}}++: {{Free}} Antispy Tool for {{Windows}} 10 and 11}, shorttitle = {O\&{{O ShutUp10}}++}, author = {O\&O Software}, journal = {O\&O Software GmbH}, urldate = {2025-11-05}, abstract = {With this tool you have full control over which comfort functions under Windows 10 and Windows 11 you wish to use, and you decide when the passing on of your data goes too far.}, howpublished = {https://www.oo-software.com/en/shutup10}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/PNREDM62/shutup10.html} } @misc{OPNsenseOpenSourcea, title = {{{OPNsense}}\textregistered{} Is an Open Source, Feature Rich Firewall and Routing Platform, Offering Cutting-Edge Network Protection. - {{OPNsense}}}, urldate = {2025-11-07}, howpublished = {https://opnsense.org/}, file = {/home/jehaverlack/Zotero/storage/GP2BNW3M/opnsense.org.html} } @misc{OSCALOpenSecurity, title = {{{OSCAL}} - {{Open Security Controls Assessment Language}}}, urldate = {2025-11-07}, howpublished = {https://pages.nist.gov/OSCAL/}, file = {/home/jehaverlack/Zotero/storage/WL9HLSTR/OSCAL.html} } @misc{OSCALOpenSecuritya, title = {{{OSCAL}} - {{Open Security Controls Assessment Language}}}, urldate = {2025-11-21}, howpublished = {https://pages.nist.gov/OSCAL/}, file = {/home/jehaverlack/Zotero/storage/I3RHYI84/OSCAL.html} } @misc{ProgramDepartmentEnergys, title = {About {{The Program}} -- {{Department}} of {{Energy}}'s {{CyberForce}}\textregistered{} {{Program}}}, urldate = {2026-01-14}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/24GGG2GW/about-the-program.html} } @misc{ProtectliTrustedFirewall, title = {Protectli: {{Trusted Firewall Appliances}} with {{Firmware Protection}}}, shorttitle = {Protectli}, journal = {Protectli}, urldate = {2025-11-07}, abstract = {Secure your network with a trusted Protectli Firewall Appliance! Fully compatible with open-source software. US-based support, warranty and repairs.}, howpublished = {https://protectli.com/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/I874MQGZ/protectli.com.html} } @misc{ProxmoxServerSolutions, title = {Proxmox {{Server Solutions}}}, journal = {Proxmox}, urldate = {2025-09-30}, abstract = {Proxmox develops powerful and efficient open-source server solutions like the Proxmox VE platform, Proxmox Backup Server, and Proxmox Mail Gateway.}, howpublished = {https://www.proxmox.com/en/}, langid = {british}, file = {/home/jehaverlack/Zotero/storage/8SMGZTGL/en.html} } @misc{ProxmoxServerSolutionsa, title = {Proxmox {{Server Solutions}}}, journal = {Proxmox}, urldate = {2025-11-07}, abstract = {Proxmox develops powerful and efficient open-source server solutions like the Proxmox VE platform, Proxmox Backup Server, and Proxmox Mail Gateway.}, howpublished = {https://proxmox.com/en/}, langid = {british} } @misc{ProxmoxVirtualEnvironment, title = {Proxmox {{Virtual Environment}} - {{Open-Source Server Virtualization Platform}}}, urldate = {2025-11-07}, howpublished = {https://www.proxmox.com/en/products/proxmox-virtual-environment/overview}, file = {/home/jehaverlack/Zotero/storage/5WXIHL54/overview.html} } @misc{PublicationsCSRC, title = {Publications \textbar{} {{CSRC}}}, urldate = {2025-11-07}, howpublished = {https://csrc.nist.gov/publications}, file = {/home/jehaverlack/Zotero/storage/V2PZHFQS/publications.html} } @article{PurdueEnterpriseReference2024, title = {Purdue {{Enterprise Reference Architecture}}}, year = 2024, month = sep, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Purdue Enterprise Reference Architecture (PERA), or the Purdue model, is a 1990s reference model for enterprise architecture, developed by Theodore J. Williams and members of the Industry-Purdue University Consortium for Computer Integrated Manufacturing.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1247976469}, file = {/home/jehaverlack/Zotero/storage/HNGN6XP4/index.html} } @misc{RaspberryPiGPIO, title = {Raspberry {{Pi GPIO Pinout}}}, urldate = {2025-11-05}, howpublished = {https://pinout.xyz/}, file = {/home/jehaverlack/Zotero/storage/C7J7IV4S/pinout.xyz.html} } @misc{RegulatoryCommissionAlaska, title = {Regulatory {{Commission}} of {{Alaska}}}, urldate = {2025-11-07}, howpublished = {https://rca.alaska.gov/RCAWeb/home.aspx}, file = {/home/jehaverlack/Zotero/storage/FJ56WR35/home.html} } @misc{RegulatoryCommissionAlaskaa, title = {Regulatory {{Commission}} of {{Alaska}}}, urldate = {2025-12-08}, howpublished = {https://rca.alaska.gov/RCAWeb/home.aspx}, file = {/home/jehaverlack/Zotero/storage/Z79D644F/home.html} } @article{ReliabilityAvailabilityServiceability2025, title = {Reliability, Availability and Serviceability}, year = 2025, month = sep, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Reliability, availability and serviceability (RAS), also known as reliability, availability, and maintainability (RAM), is a computer hardware engineering term involving reliability engineering, high availability, and serviceability design. The phrase was originally used by IBM as a term to describe the robustness of their mainframe computers. Computers designed with higher levels of RAS have many features that protect data integrity and help them stay available for long periods of time without failure. This data integrity and uptime is a particular selling point for mainframes and fault-tolerant systems.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1309329425}, file = {/home/jehaverlack/Zotero/storage/E4A3GQEC/index.html} } @misc{ReliabilityStandards, title = {Reliability {{Standards}}}, urldate = {2025-11-07}, howpublished = {https://www.nerc.com/pa/Stand/Pages/ReliabilityStandards.aspx}, file = {/home/jehaverlack/Zotero/storage/U7FJWIRX/ReliabilityStandards.html} } @misc{ResearchCybersecurity, title = {Research {{Cybersecurity}}}, urldate = {2025-10-23}, abstract = {Project Objectives This project will address these challenges through four primary planning objectives: Map the current research cybersecurity meta landscape by assembling federal policy, agency resources, institutional expectations, and documented cybersecurity threats affecting research. Examine}, howpublished = {https://www.researchcybersecurity.org/}, langid = {american}, keywords = {InfoSec,Research}, file = {/home/jehaverlack/Zotero/storage/LYBKUYPF/www.researchcybersecurity.org.html} } @techreport{roseZeroTrustArchitecture2020, title = {Zero {{Trust Architecture}}}, author = {Rose, Scott and Borchert, Oliver and Mitchell, Stu and Connelly, Sean}, year = 2020, month = aug, number = {NIST Special Publication (SP) 800-207}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-207}, urldate = {2025-11-07}, abstract = {Zero trust (ZT) is the term for an evolving set of cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users, assets, and resources. A zero trust architecture (ZTA) uses zero trust principles to plan industrial and enterprise infrastructure and workflows. Zero trust assumes there is no implicit trust granted to assets or user accounts based solely on their physical or network location (i.e., local area networks versus the internet) or based on asset ownership (enterprise or personally owned). Authentication and authorization (both subject and device) are discrete functions performed before a session to an enterprise resource is established. Zero trust is a response to enterprise network trends that include remote users, bring your own device (BYOD), and cloud-based assets that are not located within an enterprise-owned network boundary. Zero trust focuses on protecting resources (assets, services, workflows, network accounts, etc.), not network...}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/EHSG3HYE/Rose et al. - 2020 - Zero Trust Architecture.pdf} } @techreport{rossProtectingControlledUnclassified2021, title = {Protecting {{Controlled Unclassified Information}} in {{Nonfederal Systems}} and {{Organizations}}}, author = {Ross, Ron and Pillitteri, Victoria and Dempsey, Kelley and Riddle, Mark and Guissanie, Gary}, year = 2021, month = jan, number = {NIST Special Publication (SP) 800-171 Rev. 2 (Withdrawn)}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-171r2}, urldate = {2025-11-07}, abstract = {The protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the federal government to successfully conduct its essential missions and functions. This publication provides agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations; when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency; and where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or governmentwide policy for the CUI category listed in the CUI Registry. The requirements apply to all components of nonfederal systems and organizations that process, store, and/or transmit CUI, or that provide...}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/CC2SHWBG/Ross et al. - 2021 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.pdf} } @techreport{rossProtectingControlledUnclassified2023, title = {Protecting {{Controlled Unclassified Information}} in {{Nonfederal Systems}} and {{Organizations}}}, author = {Ross, Ron and Pillitteri, Victoria}, year = 2023, month = may, number = {NIST Special Publication (SP) 800-171 Rev. 3 (Withdrawn)}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-171r3.ipd}, urldate = {2025-11-07}, abstract = {The protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations, when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency, and where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or governmentwide policy for the CUI category listed in the CUI Registry. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components....}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/2Y6HM6VA/Ross and Pillitteri - 2023 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.pdf} } @techreport{rossProtectingControlledUnclassified2023a, title = {Protecting {{Controlled Unclassified Information}} in {{Nonfederal Systems}} and {{Organizations}}}, author = {Ross, Ron and Pillitteri, Victoria}, year = 2023, month = may, number = {NIST Special Publication (SP) 800-171 Rev. 3 (Withdrawn)}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-171r3.ipd}, urldate = {2025-11-07}, abstract = {The protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations, when the nonfederal organization is not collecting or maintaining information on behalf of a federal agency or using or operating a system on behalf of an agency, and where there are no specific safeguarding requirements for protecting the confidentiality of CUI prescribed by the authorizing law, regulation, or governmentwide policy for the CUI category listed in the CUI Registry. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components....}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/96C54VLQ/Ross and Pillitteri - 2023 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.pdf} } @techreport{rossProtectingControlledUnclassified2023b, title = {Protecting {{Controlled Unclassified Information}} in {{Nonfederal Systems}} and {{Organizations}}}, author = {Ross, Ron and Pillitteri, Victoria}, year = 2023, month = nov, number = {NIST Special Publication (SP) 800-171 Rev. 3 (Withdrawn)}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-171r3.fpd}, urldate = {2025-11-07}, abstract = {The protection of Controlled Unclassified Information (CUI) resident in nonfederal systems and organizations is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. The security requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/JK7KFY8X/Ross and Pillitteri - 2023 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.pdf} } @techreport{rossProtectingControlledUnclassified2024, title = {Protecting {{Controlled Unclassified Information}} in {{Nonfederal Systems}} and {{Organizations}}}, author = {Ross, Ron and Pillitteri, Victoria}, year = 2024, month = may, number = {NIST Special Publication (SP) 800-171 Rev. 3}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.800-171r3}, urldate = {2025-11-07}, abstract = {The protection of Controlled Unclassified Information (CUI) is of paramount importance to federal agencies and can directly impact the ability of the Federal Government to successfully conduct its essential missions and functions. This publication provides federal agencies with recommended security requirements for protecting the confidentiality of CUI when the information is resident in nonfederal systems and organizations. The requirements apply to components of nonfederal systems that process, store, or transmit CUI or that provide protection for such components. The security requirements are intended for use by federal agencies in contractual vehicles or other agreements established between those agencies and nonfederal organizations. This publication can be used in conjunction with its companion publication, NIST Special Publication 800-171A, which provides a comprehensive set of procedures to assess the security requirements.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/URLQVDNR/Ross and Pillitteri - 2024 - Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.pdf} } @article{ruggieroDataBackupOptions, title = {Data {{Backup Options}}}, author = {Ruggiero, Paul and Heckathorn, Matthew A}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/MHPWUG8M/Ruggiero and Heckathorn - Data Backup Options.pdf} } @article{SCADA2025, title = {{{SCADA}}}, year = 2025, month = sep, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Supervisory control and data acquisition (SCADA) is a control system architecture comprising computers, networked data communications and graphical user interfaces for high-level supervision of machines and processes. It also covers sensors and other devices, such as programmable logic controllers, also known as a distributed control system (DCS), which interface with process plant or machinery. The operator interfaces, which enable monitoring and the issuing of process commands, such as controller setpoint changes, are handled through the SCADA computer system. The subordinated operations, e.g. the real-time control logic or controller calculations, are performed by networked modules connected to the field sensors and actuators. The SCADA concept was developed to be a universal means of remote-access to a variety of local control modules, which could be from different manufacturers and allowing access through standard automation protocols. In practice, large SCADA systems have grown to become similar to DCSs in function, while using multiple means of interfacing with the plant. They can control large-scale processes spanning multiple sites, and work over large distances. It is one of the most commonly used types of industrial control systems.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1314053470}, file = {/home/jehaverlack/Zotero/storage/ICI4C42G/index.html} } @article{ScopingGuide_Level3_, title = {Scoping {{Guide}}\_{{Level3}}\_}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/29DAKNCU/Scoping Guide_Level3_.pdf} } @article{SinglePointFailure2025, title = {Single Point of Failure}, year = 2025, month = jul, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {A single point of failure (SPOF) is a part of a system that would stop the entire system from working if it were to fail. The term single point of failure implies that there is not a backup or redundant option that would enable the system to continue to function without it. SPOFs are undesirable in any system with a goal of high availability or reliability, be it a business practice, software application, or other industrial system. If there is a SPOF present in a system, it produces a potential interruption to the system that is substantially more disruptive than an error would elsewhere in the system.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1301375012}, file = {/home/jehaverlack/Zotero/storage/J8IHKZG7/index.html} } @article{SoftwaredefinedDataCenter2025, title = {Software-Defined Data Center}, year = 2025, month = sep, journal = {Wikipedia}, urldate = {2025-11-07}, abstract = {Software-defined data center (SDDC; also: virtual data center, VDC) is a marketing term that extends virtualization concepts such as abstraction, pooling, and automation to all data center resources and services to achieve IT as a service (ITaaS). In a software-defined data center, "all elements of the infrastructure --- networking, storage, CPU and security -- are virtualized and delivered as a service." SDDC support can be claimed by a wide variety of approaches. Critics see the software-defined data center as a marketing tool and "software-defined hype," noting this variability. In 2013, analysts were divided into three different groups, those who think it is "just another software-defined hype", those who think most of the components are already available and those who see a potential future market. There was no unified agreement about the direction of SDDC. For some areas like the software-defined networking a market value of about US\$3.7 billion by 2016 was expected, compared to US\$360 million in 2013. (software-defined networking was expected to reach US\$18.5 billion in 2022) IDC estimates that the software-defined storage market is poised to expand faster than any other storage market.}, copyright = {Creative Commons Attribution-ShareAlike License}, langid = {english}, annotation = {Page Version ID: 1312263478}, file = {/home/jehaverlack/Zotero/storage/SMUAUL97/index.html} } @misc{StepcaCertificateAuthority, title = {Step-ca {{Certificate Authority Overview}} \textbar{} {{Smallstep}}}, urldate = {2025-11-07}, abstract = {Complete documentation for step-ca certificate authority. Deploy and manage your own private CA for enterprise PKI operations.}, howpublished = {https://smallstep.com/docs/step-ca/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/JDVYP4LX/step-ca.html} } @techreport{stoneITAssetManagement2018, title = {{{IT Asset Management}}}, author = {Stone, Michael and Irrechukwu, Chinedum and Perper, Harry and Wynne, Devin and Kauffman, Leah}, year = 2018, month = sep, number = {NIST Special Publication (SP) 1800-5}, institution = {{National Institute of Standards and Technology}}, doi = {10.6028/NIST.SP.1800-5}, urldate = {2025-11-07}, abstract = {While a physical asset management system can tell you the location of a computer, it cannot answer questions like, ``What operating systems are our laptops running?'' and ``Which devices are vulnerable to the latest threat?'' An effective IT asset management (ITAM) solution can tie together physical and virtual assets and provide management with a complete picture of what, where, and how assets are being used. ITAM enhances visibility for security analysts, which leads to better asset utilization and security.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/82LC7ZL3/Stone et al. - 2018 - IT Asset Management.pdf} } @misc{TailscaleBestVPN, title = {Tailscale {$\cdot$} {{Best VPN Service}} for {{Secure Networks}}}, urldate = {2025-11-07}, abstract = {Securely connect to anything on the internet with Tailscale. Deploy a WireGuard\textregistered -based VPN to achieve point-to-point connectivity that enforces least privilege.}, howpublished = {https://tailscale.com}, file = {/home/jehaverlack/Zotero/storage/VM6PB68W/tailscale.com.html} } @misc{TailscaleSecureConnectivity, title = {Tailscale \textbar{} {{Secure Connectivity}} for {{AI}}, {{IoT}} \& {{Multi-Cloud}}}, urldate = {2026-01-29}, abstract = {The connectivity platform for devs, IT, and security teams. Zero Trust identity-based access that deploys in minutes and scales to every resource. Start free.}, howpublished = {https://tailscale.com}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/3THE45XX/tailscale.com.html} } @misc{teamKeycloak, title = {Keycloak}, author = {Team, Keycloak}, urldate = {2025-11-07}, abstract = {Keycloak - the open source identity and access management solution. Add single-sign-on and authentication to applications and secure services with minimum effort.}, howpublished = {https://www.keycloak.org/}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/UZ24R6MQ/www.keycloak.org.html} } @misc{TechnicalSpecifications, title = {Technical {{Specifications}}}, urldate = {2026-01-20}, abstract = {This Stream includes all of our technical specficiations}, howpublished = {https://resources.lora-alliance.org/technical-specifications}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/KJ2VKRQP/technical-specifications.html} } @techreport{technologyMinimumSecurityRequirements2006, title = {Minimum {{Security Requirements}} for {{Federal Information}} and {{Information Systems}}}, author = {and Technology, National Institute of Standards}, year = 2006, month = mar, number = {Federal Information Processing Standard (FIPS) 200}, institution = {U.S. Department of Commerce}, doi = {10.6028/NIST.FIPS.200}, urldate = {2025-11-07}, abstract = {The E-Government Act of 2002 (Public Law 107-347) recognized the importance of information security to the economic and national security interests of the United States. Title III of the E-Government Act, 'Federal Information Security Management Act (FISMA) of 2002,' tasked NIST with the responsibility of developing security standards and guidelines for the federal government. This standard---the second of two security standards mandated by FISMA---specifies minimum security requirements for information and information systems supporting the executive agencies of the federal government and a risk-based process for selecting the security controls necessary to satisfy the minimum security requirements.~This standard will promote the development, implementation, and operation of more secure information systems within the federal government by establishing minimum levels of due diligence for information security and facilitating a more consistent, comparable, and repeatable approach for...}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/MNA5I6DE/Technology - 2006 - Minimum Security Requirements for Federal Information and Information Systems.pdf} } @techreport{technologyStandardsSecurityCategorization2004, title = {Standards for {{Security Categorization}} of {{Federal Information}} and {{Information Systems}}}, author = {and Technology, National Institute of Standards}, year = 2004, month = feb, number = {Federal Information Processing Standard (FIPS) 199}, institution = {U.S. Department of Commerce}, doi = {10.6028/NIST.FIPS.199}, urldate = {2025-11-07}, abstract = {The purpose of this document is to provide a standard for categorizing federal information and information systems according to an agency's level of concern for confidentiality, integrity, and availability and the potential impact on agency assets and operations should their information and information systems be compromised through unauthorized access, use, disclosure, disruption, modification, or destruction.}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/NQCDLIML/Technology - 2004 - Standards for Security Categorization of Federal Information and Information Systems.pdf} } @misc{ThankYouRegistering, title = {Thank You for Registering for the Webinar \textbar{} {{Dragos}}}, urldate = {2026-01-06}, howpublished = {https://hub.dragos.com/thank-you/ukraine-power-grid-attack-10-year-anniversary-lessons-learned}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/VL5ZKSY2/ukraine-power-grid-attack-10-year-anniversary-lessons-learned.html} } @misc{TrafficLightProtocol2022, title = {Traffic {{Light Protocol}} ({{TLP}}) {{Definitions}} and {{Usage}} \textbar{} {{CISA}}}, year = 2022, month = aug, urldate = {2025-11-22}, howpublished = {https://www.cisa.gov/news-events/news/traffic-light-protocol-tlp-definitions-and-usage}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/WG3SJ4XX/traffic-light-protocol-tlp-definitions-and-usage.html} } @book{trefethenNumericalLinearAlgebra2022, title = {Numerical Linear Algebra}, author = {Trefethen, Lloyd N. and Bau, David}, year = 2022, series = {{{SIAM}} Textbooks}, edition = {Twenty-fifth anniversary edition}, publisher = {{siam, Society for Industrial and Applied Mathematics}}, address = {Philadelphia, PA}, isbn = {978-1-61197-715-8}, langid = {english}, file = {/home/jehaverlack/Zotero/storage/DUPJP3K5/Trefethen and Bau - 2022 - Numerical linear algebra.pdf} } @book{trefethenNumericalLinearAlgebra2022a, title = {Numerical {{Linear Algebra}}: {{Twenty-Fifth Anniversary Edition}}}, shorttitle = {Numerical {{Linear Algebra}}}, author = {Trefethen, Lloyd N. and Bau, III David}, year = 2022, publisher = {{SIAM-Society for Industrial and Applied Mathematics}}, address = {Philadelphia, PA}, abstract = {Since its original appearance in 1997, Numerical Linear Algebra has been a leading textbook in its field, used in universities around the world. It is noted for its 40 lecture-sized short chapters and its clear and inviting style. It is reissued here with a new foreword by James Nagy and a new afterword by Yuji Nakatsukasa about subsequent developments.}, isbn = {978-1-61197-715-8}, langid = {english} } @misc{trustedciDeepMachineLearning2023, title = {Deep {{Machine Learning}} for {{Intrusion Detection}} in {{Cyber-Physical Critical Infrastructures}}}, author = {{Trusted CI}}, year = 2023, month = nov, urldate = {2025-12-17}, abstract = {Creative Commons Attribution license (reuse allowed)} } @misc{TrustedCISummit, title = {Trusted {{CI Summit Report}} - 2020 {{9Dec20}} (3).Pdf}, journal = {Google Docs}, urldate = {2026-01-22}, howpublished = {https://drive.google.com/file/u/1/d/10yWQot9n96IBcGAzOXc8MG8q-MgIkO\_K/view?usp=embed\_facebook}, file = {/home/jehaverlack/Zotero/storage/EADCIVK9/view.html} } @misc{UAFHomeUniversity, title = {{{UAF Home}} \textbar{} {{University}} of {{Alaska Fairbanks}}}, urldate = {2025-11-07}, howpublished = {https://www.uaf.edu/uaf/index.php}, file = {/home/jehaverlack/Zotero/storage/CEZUNZED/index.html} } @misc{USReliabilityStandards, title = {{{US Reliability Standards}}}, urldate = {2025-11-07}, howpublished = {https://www.nerc.com/pa/Stand/Pages/USRelStand.aspx}, file = {/home/jehaverlack/Zotero/storage/6WAXCCV3/USRelStand.html} } @misc{VSCodiumOpenSource, title = {{{VSCodium}} - {{Open Source Binaries}} of {{VSCode}}}, urldate = {2025-11-11}, howpublished = {https://vscodium.com/}, file = {/home/jehaverlack/Zotero/storage/6KDLEIWF/vscodium.com.html} } @misc{WazuhOpenSource, title = {Wazuh - {{Open Source XDR}}. {{Open Source SIEM}}.}, urldate = {2025-09-30}, howpublished = {https://wazuh.com/}, file = {/home/jehaverlack/Zotero/storage/8KSEBCLM/wazuh.com.html} } @misc{WhatAreLoRa, title = {What Are {{LoRa}} and {{LoRaWAN}}?}, journal = {The Things Network}, urldate = {2025-11-07}, abstract = {Welcome to the first chapter of The Things Fundamentals on LoRaWAN. In this section, you'll learn why LoRaWAN is so awesome, hear about some great LoRaWAN use cases, and learn the difference between LoRa and LoRaWAN. LoRa LoRa is a wireless modulation technique derived from Chirp Spread Spectrum (CSS) technology. It encodes information on radio waves using chirp pulses - similar to the way dolphins and bats communicate! LoRa modulated transmission is robust against disturbances and can be received across great distances.}, chapter = {lorawan}, howpublished = {https://www.thethingsnetwork.org/docs/lorawan/what-is-lorawan/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/2MKKWSVK/what-is-lorawan.html} } @misc{WillFisherACEP, title = {Will {{Fisher}} \textbar{} {{ACEP}}}, urldate = {2025-09-30}, howpublished = {https://www.uaf.edu/acep/about/our-team/will-fisher.php} } @misc{YourPartnerOT, title = {Your {{Partner}} in {{OT Cybersecurity}} \textbar{} {{Dragos}}}, urldate = {2025-11-07}, abstract = {Secure your critical infrastructure with Dragos, our industrial cybersecurity solutions provide unmatched visibility and threat detection for OT environments.}, howpublished = {https://www.dragos.com/}, langid = {american}, file = {/home/jehaverlack/Zotero/storage/7LMLRKGL/www.dragos.com.html} }