[{"content":"Test Driven Development (TDD) Methodology Overview Test Driven Development (TDD) is a development methodology utilized by software engineers. It is particularly popular in mission critical environments with low recovery time objectives. In these cases, all code must be thoroughly tested and checked before deployment. In TDD, the developer creates tests before any other step. This defines the success, failure, and edge case behaviors before any development takes place.\nTDD follows a simple cycle:\nCreate a list of desired behaviors and outputs for a single function, class, or object. Create a test for each time on the list, start with a single case for the test. Write the simplest cod to pass the test. Refactor and refine the code prioritizing readability and maintainability, adding minimal complexity to meet the requirements. Add further test cases to account for expected failures and edge behavior. Repeat steps 4 and 5 only until the expected functionality is available. Do not go beyond the minimum possible scope. Repeat all the steps for the next function, class, or object. Before beginning TDD, the developer creates a well defined plan covering all project infrastructure, inputs, and outputs. Without clear definitions for the requirements, it becomes impossible to define sufficient tests.\nThere are a few notable benefits to using TDD. The first is that it results in high test coverage. Since the tests come first, almost every line of the program ends up covered. While this bloats the software, it ensures reliability and reduces the number of bugs in production. The next benefit is that the method produces simple and clean code. Since the goal of TDD is create the simplest code to pass the test, it results in clean and simple code. Finally, the tests act as living documentation. Before updating any code, the developer updates the tests. As a result, the tests always reflect the expected behavior of the code. Any developer can read the tests to understand the inputs, outputs, expected behavior, and edge cases. These benefits align with modern best practices in coding producing clean, high quality, and maintainable code.\nThe primary drawback for this methodology is time. This process requires extensive planning upfront. Additionally, due to stricter testing requirements, it often results in more tests overall. Which increases development time further. There is a secondary drawback of a false sense of security. There is still the potential for issues when writing tests first. The developer may miss necessary tests or fail to consider edge cases. Further, the tests only cover the smallest behavioral units. New behavior and issues will emerge when the individual components begin to act as a whole. The code requires proper functionality and implementation tests to cover the emergent cases.\nPersonally, I use this methodology frequently when programming. Well tested code is reliable, easy to maintain, and readable. Though, often, I find it results with test coverage above 95%. While higher test coverage is desirable, it is not always required. Excessive tests slow down future development causing a cascade of required changes when updating any portion of the code. Despite this, I would rather spend more time in development reducing the arduous process of debugging.\nWhile TDD is not the most popular methodology, development teams with strict testing requirements often employ it. However, the time costs is prohibitive and often drop the methodology to meet shorter deadlines or while debugging. Other development methodologies such as Data Driven Development (DDD) are more popular for this reason. These strategies are not mutually exclusive and teams often decide on the most appropriate approach for their current situation. Swapping between different methodologies and development strategies as necessary.\nI recommend all developers, especially those new to programming or a programming language, utilize TDD. The strict framework allows for robust infrastructure and emphasizes the need for clean and simple code.\nCopyright Notice Copyright © 2026 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/test_driven_development/","summary":"TDD methodology for software development teams.","title":"Test Driven Development (TDD)"},{"content":"STRIDE Threat Model Threat modeling is the proactive practice of analyzing potential risks and threats while utilizing a system or application for active identification and mitigation [1]. Threat modeling focuses on analyzing the weaknesses in a system from the point of view of an attacker to reduce risk. This process results in a list of threats as well as their priority. Allowing for teams to meaningfully reduce risk by addressing the most prevalent and pervasive threats first.\nThere are many threat modeling frameworks worth exploring. I will focus on the STRIDE model today but encourage readers to explore alternatives such as PASTA, LINDDUN, and RRA. The STRIDE threat modeling framework is a systematic approach used to identify and analyze potential threats and vulnerabilities within a software system [1]. STRIDE is somewhat broad for a threat modeling framework. Other models, such as Mozilla\u0026rsquo;s RRA, focus on smaller software components. Despite the broader scope of STRIDE, I find it captures the threats to the security properties laid out in the CIA triad and Parkerian Hexad.\n_note: See my posts on the CIA Triad and Parkerian Hexad for more detailed discussions of the topics.\nSTRIDE stands for Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege. Each piece of the acronym represents a common threat to one of the key properties of security. Figure 1, below, shows each property, the corresponding threat, as well as an example of the threat [2].\nFigure 1: STRIDE Model Chart [2] To implement STRIDE (or most other threat models), there are a few simple steps. First, gather the target system information including the name, description, data utilized, scope of interaction, and workflows [1]. While doing so, collect any available information regarding the organization and system data flow. Next, identify the key stakeholders [1]. It is crucial to understand those who work on and with the system to maintain the system function while ensuring its security. Finally, identify threats against the system using the STRIDE model as a guide. This could be accomplished through Confluence, written reports, or meetings with the security team and stakeholders. After walking through each of the STRIDE threats and documenting it, order them by risk and impact to create a mitigation plan. Repeat the process to ensure the system remains up to date with the current threat landscape.\nThreat modeling is essential for maintaining the security of information system and services. Without consideration of the current threat landscape for a system, it is impossible to adequately prepare security. Modeling threats and creating tailored mitigation plans reduces the total resource cost of security while ensuring the system is safe against the highest risk attack vectors. Security teams should regularly re-model the threats against their systems to ensure they stay up to date.\nPersonally, I recommend STRIDE as a starting point for anyone looking into threat modeling. While simplified compared to other modern methodologies, it focuses on the key security properties applicable to digital and physical security environments. Further, I recommend teams create their own threat models based on information from their system logs and open source intelligence on the advanced persistent threats (APTs) in their industry.\nSources [1] “CMS Threat Modeling Handbook | CMS Information Security and Privacy Program,” Cms.gov, 2024. https://security.cms.gov/learn/cms-threat-modeling-handbook\n[2] M. Security, “STRIDE chart,” Microsoft Security Blog, Sep. 11, 2007. https://www.microsoft.com/en-us/security/blog/2007/09/11/stride-chart/\nCopyright Notice Copyright © 2026 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/stride/","summary":"An explanation of the STRIDE threat model.","title":"STRIDE Threat Model"},{"content":"Parkerian Hexad The CIA triad, shown in Figure 1 below, likely1 originated in the 1970\u0026rsquo;s as a response to the digitization of physical records [1]. It is a framework that emphasizes three primary security objectives: Confidentiality, Integrity, and Availability. Balancing these three objectives is crucial in maintaining private, secure, and usable systems. While the CIA triad is primarily applied to digital security, the concepts transfer to physical security systems well.\nnote: See my previous post on the CIA triad for a more detailed discussion of the topic\nFigure 1: CIA Triad [2] In the 1990\u0026rsquo;s, cybersecurity began to evolve as a field. Digitization coinciding with the origination of the internet necessitated new technologies and methodologies for securing information. During this time, Donn B. Parker, proposed a new framework to replace the overly simplified CIA framework [3]. It became known as the Parkerian Hexad, shown in Figure 2 below, and adds three new components to the triad: Possession/Control, Authenticity, and Utility.\nFigure 2: Parkerian Hexad [4] The first addition is Possession or Control, which is an expansion to Confidentiality from the CIA triad. Confidentiality focuses on the preservation of authorized accessed to restricted information such as personal or proprietary information. Parker shows there are few important security considerations missed by this narrow definition. For instance, the theft of confidential information without disclosure or observation does not violate confidentiality [3]. Yet, the information is still lost or could potentially be held for ransom. A practice which became common with crypto ransomware in the early 2010\u0026rsquo;s. Both the Petya ransomware and the LastPass breaches are famous examples of this type of loss. Information remained confidential while the attackers possessed it. Parker emphasizes the important of Possession or Control over confidential information within the hexad. Confidentiality on its own is insufficient to cover the modern threat landscape.\nThe next addition is Authenticity, which acts as an expansion to Integrity. Parker states that integrity focuses on the soundness or state of an object without considering the preservation of content or meaning [3]. For example, hardware degradation could result in a readable data modification. This would not cause a loss of integrity, as all data remains in intact, but a loss of authenticity due to the improper modification. For data to be usable, it must maintain both integrity and authenticity. Further, Parker expands Integrity to cover non-repudiation or the inability of the sender to deny the authenticity of the object. False repudiation of data does not compromise the data\u0026rsquo;s integrity instead it compromises its authenticity. Integrity focuses on the condition of the data while authenticity focuses on the validity [3]. The security controls required for each of these concepts differ and consideration for both is necessary to preserve data in a meaningful and usable manner.\nThe final addition is Utility, which acts as an expansion to Availability. Availability ensures timely and reliable^[2] access to data [3]. While the data may be available, it fails to consider the state of the data. If the data is improperly formatted or encrypted, the end user will not be able to utilize it. Inability to utilize the data negates its availability. Further, if the format of the data is unusable, then the integrity of the data is meaningless. If all data is intact in a file format that is no longer readable, then the data is lost. Demonstrating that availability is too narrow to account for all modern scenarios.\nThe Parkerian Hexad is relatively unknown in comparison to the popular CIA triad. The CIA triad is widely taught due to its simplicity and capture of the essential trade offs of security. Perfectly confidential data is useless if no one can access it, accessible data is meaningless if it lacks integrity, and integral data is insecure if it\u0026rsquo;s all public. Parker does not refute the accuracy or usefulness of the CIA triad but instead expands it to cover modern threats and considerations, many of which did not exist during the inception of the CIA triad.\nPersonally, I find the Parkerian Hexad more applicable to modern information security and threat modeling discussions. The CIA triad, while beneficial, is overly simplified for the internet age. As technology evolves, our model of information security must keep pace. Today\u0026rsquo;s threat landscape is more diverse than ever. Attackers are intelligent, dedicated, observant, and may have substantial resources. We must use a more complete model to keep pace. The Parkerian Hexad is the best proposal I have seen for such a model so far.\nSources [1] Jim Holdsworth and M. Kosinski, “Information Security,” Ibm.com, Jul. 26, 2024. https://www.ibm.com/think/topics/information-security\n[2] https://i0.wp.com/thecyberthrone.in/wp-content/uploads/2025/06/file_00000000311461f684ba4c98c9c92d2d4829824476695499797.png?resize=1024%2C1024\u0026ssl=11 (accessed Mar. 26, 2026).\n[3] Parker, Donn B. “Our Excessively Simplistic Information Security Model and How to Fix It.” Information Systems Security Association, vol. 8, no. 7, July 2010, pp. 12–21.\n[4] G. Pender-Bey, “THE PARKERIAN HEXAD,” 2019. Available: https://cs.lewisu.edu/mathcs/msisprojects/papers/georgiependerbey.pdf\nFootnotes Copyright Notice Copyright © 2026 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\nThere is some disagreement on the origins of the CIA triad. IBM claims to have invented it in the 1970\u0026rsquo;s but there are several competing claims. Some historians go as far as tracing it back to the origins of information security in the Roman Empire.\u0026#160;\u0026#x21a9;\u0026#xfe0e;\n","permalink":"https://pearsonify.github.io/posts/parkerian_hexad/","summary":"An explanation of the Parkerian Hexad\u0026rsquo;s expansion to the CIA triad.","title":"Parkerian Hexad"},{"content":"Kerckhoff\u0026rsquo;s Principles note: I will be translating any references, names, or information from the original French into English. I apologize if my translations are inaccurate, please submit any feedback on GitHub if you find errors.\nIn 1883, Auguste Kerckhoff published an article in the Journal of Military Science (Journal des sciences militaires) titled \u0026ldquo;Military Cryptography\u0026rdquo; (La Cryptographie Militaire) covering his six principles of military ciphers [1]. Today, these principles form the foundation of modern electronic cryptography. Here are six principles in full:\nKerckhoff\u0026rsquo;s Principles (Translated from French) [2]\nThe system must be substantially, if not mathematically, undecipherable; The system must not require secrecy and can be stolen by the enemy without causing trouble; It must be easy to communicate and retain the key without the aid of written notes, it must also be easy to change or modify the key at the discretion of the correspondents; The system ought to be compatible with telegraph communication; The system must be portable, and its use must not require more than one person; Finally, given the circumstances in which such system is applied, it must be easy to use and must neither stress the mind or require the knowledge of a long series of rules. While all six principles remain relevant, the second is foundational. An adversary with a full understanding of the system should not be able to compromise an individual cipher. This means both the system utilized for encryption as well as the encrypted message could be communicated publicly without any un-intended recipient deciphering the message. Obscurity is not security and privacy will not secure a message.\nIn modern cryptography, we meet the standard of the second principle using problems that are only solvable with certain pieces of information; most often, the discrete log problem. Thousands work on breaking modern cryptosystems every day utilizing decades of public work and discussion. Yet, the security of encrypted information remains. Mistakes in procedure or bugs in management cause more decryptions than mathematical compromise. The public discourse around the systems causes continual improvements in security and reliability. None of which would be possible if Kerckhoff\u0026rsquo;s second principle did not hold.\nnote: See my post on the discrete log problem for a thorough discussion.\nThe first principle provides the goal for ciphers - keep the information secret. This is the only item on the list that I find lacking a component. There are two goals for all ciphers that are particularly relevant in the digital age. Keep the information secret and intact. Partial or corrupted transmission of the message renders the information useless or worse - dangerous. All modern cryptosystems accomplish both goals.\nThe third principle focuses on the portability and maintenance of the system. The first piece states: \u0026ldquo;It must be easy to communicate and retain the key without the aid of written notes.\u0026rdquo; This is vital for all cryptographic systems. The users of the system should maintain access over the key in a portable manner. It is possible to store the information and full key together while maintaining secrecy through a password or passphrase. Thus maintaining this principle. The second piece states: \u0026ldquo;It must also be easy to change or modify the key at the discretion of the correspondents.\u0026rdquo; While the second portion remains important, it should always be possible to change the key, it is not required that it is easy in all cases. Modern at rest symmetric cryptography requires substantial effort to change the key but the information remains secure. While in public key or asymmetric cryptosystems, changing the key is a trivial action. This piece of the principle remains important but does not apply equally to all cases.\nThe remaining three principles, 4-6 in the above list, require some modernization. Here are my modified versions of the principles: 4. The system ought to be compatible with digital systems; 5. It must be possible to automate and transfer the system, further its use must not require more than one person; 6. Finally, given the circumstances in which such system is applied, it must be easy to use, safe to install, and friendly for non-technical users to operate. I changed each of the principles to account for the digital revolution. Principle 4 states that these systems should be digitally compatible. Most modern systems are exclusively digital. A user cannot perform the calculations required in any reasonable fashion. All analog discussion of cryptography is through the lens of modern mathematical theory. Principle 5 states that the system should be portable and usable by a single user. Any modern cryptosystem should be transferrable between computers or across networks. If a system is not available, then it is not usable. Finally, principle 6 states that the system should be easy to use. Digital tools for cryptography accomplish this goal. Further, for a system to be safe and secure, the tool should be transparent in its operations and preferably open source. Allowing for any individual to interrogate, investigate, and modify the tool to ensure their privacy and security. All three of these principles remain not only relevant but vital today.\nThe influence of these principles on modern information systems cannot be understated. These principles form the foundation for the secure transfer of information. All secure cryptosystems follow these rules and any future systems will as well.\nSources [1] A. Kerckhoffs, “La cryptographie militaire,” Journal des sciences militaires, vol. IX, pp. 5–38.\nnote: Full article available online in both English and French\n[2] “The information hiding homepage,” The information hiding homepage, 2020. https://www.petitcolas.net/kerckhoffs/index.html (accessed Mar. 27, 2026).\nCopyright Notice Copyright © 2026 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/kerckhoff_principles/","summary":"Fundamental principles of ciphers and cryptography.","title":"Kerckhoff's Principles"},{"content":"Introduction I will briefly cover the popular lines of one of my favorite chess openings, the knight attack variant of the Italian game. The Italian game is one of the most analyzed openings in chess with over 400 years of history. Originally developed in the 1620\u0026rsquo;s, the methods for approaching the opening change every few years and have since its inception. There are entire books written on portions of the mainline alone covering few variants. This depth of analysis and steady popularity for over 4 centuries may lead one to believe the opening has a daunting reputation. Yet, due to its sound fundamentals, the opening is often recommended to beginner e4 players.\nNote on Opening Line Naming The knight attack is a term used in several chess openings. Often, this term refers to any line where black uses the two knight\u0026rsquo;s defense and white aggressively attacks utilizing either knight. As a result, the knight attack I am discussing is often referred to as the two knights defense.\nWhy I Use the Knight Attack This opening acts as a great weapon in the Italian game. As I mentioned previously, the Italian game is one of the most deeply analyzed openings in chess. Experienced players will have thousands of games played in the various possible positions, especially since it is recommended to beginner players around the world. Further, the Italian game is a popular choice for experienced e4 players due to the dangerous lines in the Spanish game and simply its fundamental strength. The knight attack breaks away from the popular mainline theory into a much less known sideline of the opening throwing opponents into complex positions with many attack opportunities. Personally, I am an aggressive player and appreciate dynamic positions that allow for interesting attacks. I find the knight attack often leaves me in those exact positions.\nEntering the position The knight attack emerges out of the Italian game when black plays the two knight defense. From the position shown below, both the knight attack and the fried liver are possible variants.\n1 2 3 4 . . . . e N B N 4 f c g 3 4 5 N N e c f 5 6 6 The Fried Liver From here, there is only one move that black can make, 4. .. d5. After 5. exd5 there is a famous mistake that black can make, 5. .. Nxd5, retaking the pawn with the knight. This seems natural for most beginners as it is the only way for black not to lose material. This leaves white with a powerful move, Nxf7, fully sacrificing the knight and forcing black to compromise the safety of their king or lose material. This variant is known as the fried liver attack. Here is the full line showing black\u0026rsquo;s infamous mistake:\n1 2 3 4 5 6 7 8 9 1 . . . . . . . . . 0 . e N B N e N Q N O d 4 f c g x x f c - 4 3 4 5 d f 3 3 O 5 7 + N N d N c e c f 5 N K K b 6 5 6 6 x x e 4 d f 6 5 7 The final result of the above position (where black makes all the best moves possible after Nxf7) leaves white with a substantial positional advantage. The black king is stuck in the center of the board with few options for defense while white can quickly mobilize more forces to attack the center. Additionally, white is further developed and their pieces are in more active positions. Although the variant ends with white down a piece for a pawn, white gains substantial compensation and ends with a much stronger position.\nMain Lines of the Knight Attack Lets return to the first position discussed and consider black\u0026rsquo;s best response, 5. .. Ka5. This line gives up a pawn to white and challenges them to hold onto that extra material. In most lines, black will win back material and equalize quickly. Leaving a balanced but complex board state with lots of dynamic potential for attacks from both sides.\n1 2 3 4 5 6 7 8 . . . . . . . . e N B N e B d B 4 f c g x b x d 3 4 5 d 5 c 3 5 + 6 N N d e c f 5 N c b 5 6 6 a 6 x 5 c 6 From here, black only has one move that equalizes, 8. .. Nd5. This leaves white with the choice of how the game will go. There are two popular lines, but I will recommend the following one where white plays 9. h4. This move leads to an immediate attack from white taking advantage of black\u0026rsquo;s scattered position.\nBy advanced h4, white begins an attack on the black king. Due to the broken pawn chain on the queenside, black is unable to castle queenside without severely compromising the safety of their king. Causing white\u0026rsquo;s kingside attack to be an immediate threat. Further, in depth analysis in hundreds of thousands of positions across different openings, made possible by modern server processors, shows that advancing the h pawn does not compromise the safety of the king after castling kingside. Not to give too much credit to computers for this position, it is a classical piece of knowledge in chess that a pawn being on a square or not does not improve the defense of the square itself. This is simply because pawns can only attack squares diagonally to their current position. Returning to the position at hand, this implies white can safely castle kingside as castling queenside while black has the open b file is too dangerous to consider.\nFinally, this line allows white to take and hold the initiative. White forces an immediate defense from black pressuring the king with an immediate checkmate threat. Even with the optimal defense from black, white remains in control of the game and will continue to add pressure to the kingside. While the computer rates the position is equal, it leaves black in an uncomfortable situation during the game.\n1 2 3 4 5 6 7 8 9 1 1 . . . . . . . . . 0 1 . . e N B N e B d B h Q N 4 f c g x b x d 4 h e 3 4 5 d 5 c 3 5 4 5 + 6 N N d N Q Q e c f 5 N c b d h f e 5 6 6 a 6 x 5 6 6 6 5 c 6 The other popular line is 9. f3 which leads to a more positionally driven game. Shown below, white retreats from their initial attack and focuses on developing their position and preventing a counterattack from black.\nWhile this position does not result in an immediate attack, it provides white plenty of opportunities to attack and undermine black\u0026rsquo;s hold on the center. This is a possibility due to the position of the knights and the open e file for white. Both Ne4 and Re1 provide continuations where white begins an attack on the center.\n1 2 3 4 5 6 7 8 9 1 1 1 . . . . . . . . . 0 1 2 . . . e N B N e B d B N O N c 4 f c g x b x d f - c x 3 4 5 d 5 c 3 3 O 3 d 5 + 6 3 N N d N B N N e c f 5 N c b d d f x O 5 6 6 a 6 x 5 6 4 d - 5 c 3 O 6 Conclusion While I find that this line is not often allowed in my games, as black will often play 3. .. Bc5 over 3. .. Nf6, it remains a useful weapon. Further, one can develop an attacking repertoire within the Italian game by pairing the knight attack with Evan\u0026rsquo;s gambit. Evan\u0026rsquo;s gambit is only possible after 3. .. Bc5 and gambits the b pawn by playing b4, attacking the bishop immediately and leading to aggressive attacks from white. As 3. .. Bc5 and 3. .. Nf6 are the most popular and most viable moves from black, with this repertoire, white is consistently in an early attacking position.\nI find this opening to be a great way to break out of the deep Italian theory. Hopefully you try it out and enjoy it too!\nCopyright Notice Copyright © 2026 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/knight_attack/","summary":"Overview of the knight attack opening.","title":"Knight Attack"},{"content":"Summary As a Sr. Software Engineer at Deca Technologies, I developed tools and algorithms for semiconductor package design and electronics manufacturing, using Rust and Python. I further mentored other engineers in Rust, including best practices, modern techniques, and product architecture. I have a B.S. in Mathematics from Arizona State University, where I also led a volunteer project to create a software toolkit for biological research, teaching students how to program in R and Python, plan and manage agile projects, and document software. I have interests in computational math, computer science, and cybersecurity, and I hold a CompTIA Security+ ce certification. I am passionate about solving complex problems, learning new technologies, and contributing to innovative solutions.\nCurrently, I work as a validation engineer and technical auditor for Charles Schwab. I ensure technologies are appropriately utilized, documented, and deployed. I validate the team follows their stated operating procedures and assist teams in finding solutions to issues with their processes or technologies.\nExperience System Validation Engineer Charles Schwab March 2024 - Present\nAuditing code, network infrastructure, and vendor technologies reducing risk to financial portfolios Providing recommendations and action plans to reduce technological and security risk Preparing reports on risks associated with the technological infrastructure of mathematical models Challenging established technological security protocols including access and data management Validating procedures and protocols associated with technological security and infrastructure risk Security System Specialist II Douglas County School District Aug 2024 - March 2025 (8 months)\nPrepare technical documentation for new hybrid cyber and hardware security solutions Train security staff on technologies, equipment, and standard operating procedures Maintain security devices at over 100 unique sites spread throughout Douglas county Collaborate with both security and administrative staff to develop new standards and protocols Successfully deployed new security technologies at over 75 sites ensuring student safety Design Automation Software Systems Engineer Deca Technologies Jan 2021 - July 2024 (3 years 7 months)\nUtilizing agile methodologies and github version management to reliably deliver software Programming in Rust and Python to develop software tools for semiconductor package design and ensure manufacturability Working to maintain interfaces from Rust to C and C++ to increase performance and create consistent data structures across multiple teams and projects Mentoring other engineers in Rust including best practices, modern software development, and product architecture Deployed new software refactors increasing performance, test coverage, and implementing simulation - Working with internal and external customers to continually support new features while ensuring maintainability Responsible for architecture of multiple projects including internal libraries that connect multiple teams - Responsible for cross-team development efforts of libraries to ensure compatibility while increasing performance Factory Automation Software Systems Engineer Deca Technologies Nov 2018 - Jan 2021 (2 years 3 months)\nWorked in Rust and Python to develop tools, algorithms, and heuristics for electronics manufacturing Taught other programmers how to use Rust and implement software while maintaining best practices Designed new algorithms and software to assist with semiconductor package production and increased yield Helped in web development using React.js, javascript, and HTML to create an interface to factory tools - Managed and supported computing systems deployed internationally using AWS and Docker Worked with Jenkins and Github CI to ensure accuracy of new software before deployment guaranteeing 100% uptime Responsible for international onsite verification of software performance standards Volunteer Project Manager Arizona State University Aug 2017 - May 2019 (1 year 10 months)\nLead a team of students, architecting and implementing a software toolkit for biological research Taught a team of students skills including: how to program in both R and Python, plan and manage agile projects, use the unix shell, use git, and document software using typesetting languages including Markdown and LaTeX Junior Software Engineer Deca Technologies Jun 2018 - Nov 2018 (6 months)\nWorked in Rust and Python to develop tools, algorithms, and heuristics for electronics manufacturing Worked to maintain legacy code written in lua, C, and scala Worked as part of an agile development team using Github, Jenkins, and Jira for version management - Worked to create, manage, and support distributed computing systems deployed internationally Cyber Operations, Analysis, and Research Intern in the HS-STEM Program Argonne National Laboratory May 2017 - Aug 2017 (4 months)\nPosition supported by the Department of Energy at Argonne National Laboratory Designed, authored, tested, and deployed a semi-passive TCP/IP vulnerability scanning tool based on open-source intelligence techniques, utilizing emerging techniques in the field Neuroscience Lab Intern ASU Biodesign Institute Jul 2015 - Dec 2016 (1 year 6 months)\nPhotographed brain tissue using a confocal laser microscope to understand Alzheimer\u0026rsquo;s effects on the shape of neuronal heads Education Arizona State University Bachelor of Science - BS, Mathematics 2014 - 2018\nGraduated May 2018 from Arizona State University\u0026rsquo;s Barrett Honors College with a bachelor\u0026rsquo;s degree in Mathematics. Licenses \u0026amp; Certifications CompTIA Security+ ce Certification - CompTIA Issued Jul 2021 - Expired Jul 2024\nSkills Computational Mathematics • Software Design • Project Management • Algorithm Design • Site Reliability Engineering • Design automation • Information Security • Network Security • Team Management • Software Infrastructure • Process Automation\nLinks LinkedIn Profile Github\n","permalink":"https://pearsonify.github.io/resume/","summary":"\u003ch2 id=\"summary\"\u003e\u003cstrong\u003eSummary\u003c/strong\u003e\u003c/h2\u003e\n\u003chr\u003e\n\u003cp\u003eAs a Sr. Software Engineer at Deca Technologies, I developed tools and algorithms for semiconductor package design and electronics manufacturing, using Rust and Python. I further mentored other engineers in Rust, including best practices, modern techniques, and product architecture. I have a B.S. in Mathematics from Arizona State University, where I also led a volunteer project to create a software toolkit for biological research, teaching students how to program in R and Python, plan and manage agile projects, and document software. I have interests in computational math, computer science, and cybersecurity, and I hold a CompTIA Security+ ce certification. I am passionate about solving complex problems, learning new technologies, and contributing to innovative solutions.\u003c/p\u003e","title":"Cass Pearson's Resume"},{"content":"Introduction The National Institute of Standards and Technology (NIST) maintains important publications about risk management and security. Furthering its mission to promote innovation and industrial competitiveness[1]. Special publication (SP) 800-39 \u0026lsquo;Managing Information Security Risk: Organization, Mission, and Information System View\u0026rsquo; is one of the most notable. The target audience is any individual or organization associated with the design, development, implementation, assessment, operation, maintenance, and disposition of information systems [2]. The focus is on providing guidance for an integrated, organization wide program of managing information security risk. Applying to all organizational operations (function, image, and reputation)[2]. Expaning upon the risk management framework (RMF) described in NIST SP800-37 \u0026lsquo;Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy\u0026rsquo;. I preivously summarized NIST SP800-37. I recommend becoming familiar with that article before continuing.\nSources are cited below, original article available free of charge here.\nPurpose of Publication Quoting the publication:\n\u0026ldquo;The purpose of Special Publication 800-39 is to provide guidance for an integrated, organization-wide program for managing information security risk to organizational operations (i.e., mission, functions, image, and reputation), organizational assets, individuals, other organizations, and the Nation resulting from the operation and use of federal information systems. Special Publication 800-39 provides a structured, yet flexible approach for managing risk that is intentionally broad-based, with the specific details of assessing, responding to, and monitoring risk on an ongoing basis provided by other supporting NIST security standards and guidelines.\u0026quot;[2]\nThis document provides details on the NIST RMF from an organizational risk perspective. Focusing less on the specific tasks and organizational structure than SP800-37. But expanding on the general ideas and principles behind the RMF. This document includes: information on the tasks within each tier of the RMF, details on specific terms and functions (i.e. risk executive and enterprise architecture), and information on risk management strategies. Providing means for practical implementation of the RMF\u0026rsquo;s concepts.\nFundamentals and Organizational Architecture The three tier model introduced in NIST SP800-37 includes arrows showing the flow of communication among components. The terms changed slightly from NIST800-37. Tiers become levels, but the concept is the same[3]. To review this model, consider figure 2.\nSummary of the tiers in figure 2:\nOrganization This tier focuses on governance and program-related risk management[1]. Preparing the organization to execute the RMF[3]. Here, important decisions linked to the business objectives, system modernization, enterprise architecture, and resource allocation are made. The primary responsibilities are: to understand risk, to assign roles, to identify critical functions, and to prioritize security requirements. Mission/Business Process This level focuses on the business or mission objectives. Such as defining the criticality of information flow between the organization and its partners [1]. Although related to level one, the focus is information flow, communication, and assigning task criticality. Information System This level defines the risk to information technology. Where risk to physical and digital information becomes less organizational and more practical. In figure 2 above, the arrows are not shown to be bidirectional indicating information flow. There is a continuous feedback loop for risk management policies and strategies. The organizational decisions on strategic risk are made transparently by the stakeholders within the organizational tier. While tactics used to address the risk, based on the resources allocated at the strategic level, are left to the stakeholders at the information system tier. The following diagram (figure 1) describes the communication between tiers. The bidirectional nature of the arrows indicates that the information and communication flows are flexible. Allowing for the dynamic nature of this process.[2]\nThere are four components that describe the communication between the levels of an organization[1]:\nFrame risk Defines the context for all risk activities. What are the constraints of the system? What are the organizational priorities? Assess risk The most critical aspect. Assessment of risks is continuous, thorough, and show awareness of the threat landscape. Respond to risk In responding, the threat and acceptable scope of response are apparent. Resources are allocated to stop the critical and likely threats. Monitor risk No system is perfect, no assessment can cover all threats. Monitoring for new threats is an ongoing process. As is monitoring the effectivity of existent controls. Combining figures 1 and 2, results in figure 4[2]. Demonstrating how each tier is responsible for communication and feedback within the organization.\nStakeholders decide the risk management strategy for operations to carry through. Decisions filter through several levels before put into place. The enterprise architecture communicates with information security architecture. Finally, communicating the technical security controls to operations.\nThe enterprise architecture is a management practice employed by organizations. Maximizing the effectiveness of mission/business processes and information resources [2].\nThe information security architecture is a part of the enterprise architecture. Specifically addressing information system resilience. Providing architectural information for the implementation of security controls [2].\nFinally, information security controls are the technical components. The following diagram (figure 3) shows risk management considerations as part of the enterprise architecture [2].\nFigure 3 describes how a risk management strategy decision made at tier 1 flows into operation at tier 3. Traveling through the enterprise architecture of an organization. The strategy and mission inform the enterprise architecture. Allowing for the information security architecture to create requirements and allocate resources. Resulting in the technical security control in the operation environment.\nConclusion NIST SP800-39 provides details on the organizational concepts and structures within the RMF. Focusing less on the stakeholder and tasks, instead providing methods to determine and address risk. This summary provides only a very broad conceptual outline. Omitting tasks and guidance for carrying out each step discussed in figure 1. The publication goes into detail on each of the RMF tiers. As well as related concepts such as establishing trust. This publication clarifies the concepts and ideas behind the NIST RMF. Allowing for operations staff to process the RMF.\nSources B. Chapman and F. Maymi, CompTIA CySA+ cybersecurity analyst certification all-in-one exam guide, second edition (exam CS0-002), 2nd ed. Columbus, OH: McGraw-Hill Education, 2020. Joint Task Force Transformation Initiative, “Managing information security risk :: Organization, mission, and information system view,” National Institute of Standards and Technology, Gaithersburg, MD, 2011. Joint Task Force Transformation Initiative, “Risk management framework for information systems and organizations:: A system life cycle approach for security and privacy,” National Institute of Standards and Technology, Gaithersburg, MD, 2018. Acronym Dictionary NIST: National Institute of Standards and Technology RMF: Risk Management Framework SP: Special Publication\nCopyright Notice Copyright © 2024 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/nist_sp_800-39/","summary":"NIST SP 800-39 Managing Information Security Risk summary","title":"NIST SP800-39 Managing Information Security Risk"},{"content":"Introduction NIST SP800-53 details the controls discussed in SP800-37 and SP800-39. I recommend familiarizing yourself with them before continuing. SP800-53 differs from the previous two publications by focusing on the security controls. A departure from the risk management framework(RMF)\u0026rsquo;s focus on organizational structure. This document acts as a reference for implementation of the controls described. Providing information about when to apply the control. Further including a discussion of the control, related controls, and sources. Referencing this document ensures the full control is in place. It is easy to overlook the detailed compensating and accompanying controls. This post is a guide for utilizing this document as a reference; providing context and background information.\nSources are cited below, original article available free of charge here.\nPurpose of Publication Quoting the publication:\n\u0026ldquo;This publication establishes controls for systems and organizations. The controls can be implemented within any organization or system that processes, stores, or transmits information.\u0026quot;[1]\nThis document provides details on common security controls within information systems.\nControl Structure and Example Each control within the document is assigned a category referred to as a family. \u0026ldquo;Security and privacy controls may involve aspects of policy, oversight, supervision, manual processes, and automated mechanisms that are implemented by systems or actions by individuals. Table 1 lists the security and privacy control families and their associated family identifiers.\u0026quot;[1]\nWhen implementing a security control, consider if there are necessary accompanying base controls. Diving controls up into families helps in this effort. When any control is desired, closely related controls exist in the family. Allowing for a quick check if the desired control is a base or enhancement. In practice, this shows if the desired control is sufficient alone.\nEvery control uses the structure from the diagram below [1]. The structure is self-explanatory but should be considered in detail. First, the identifier; made up of the family designation and a number. Allowing users to quickly find closely related controls. Next, the organization-defined parameters. These parameters differ based on the risk management strategy and resources allocated by the implementing organization. Finally, the related controls sections. Providing a list of closely related controls that may be compensating or enhancing.\nNow that the general structure is known, consider the following access control policy[1]:\nAs highlighted, the organizational parameters used throughout have a substantial effect. Still, the description is information rich and useful as a guide to all organizations. With references to best practices and RMF documents to determine organizational parameter values.\nConclusion Although not a technical guide on use of the tools of the trade, NIST800-53 is a practical guide for security controls. Each control is described in detail and discussed thoroughly. The only component missing is the technical \u0026ldquo;how\u0026rdquo; of applying the control. Which varies based on the information system structure and resources. All organizations should compare these controls with their documented controls.\nSources [1] Joint Task Force Interagency Working Group, “Security and privacy controls for information systems and organizations,” National Institute of Standards and Technology, 2020.\nAcronym Dictionary IR: Interagency Report OMB: Office of Management and Budget NIST: National Institute of Standards and Technology SP: Special Publication\nCopyright Notice Copyright © 2024 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/nist_sp_800-53/","summary":"NIST SP800-53 Security and Privacy Controls summary.","title":"NIST SP800-53 Security and Privacy Controls"},{"content":"Introduction The National Institute of Standards and Technology (NIST) maintains important publications about risk management and security. This is part of its mission to promote innovation and industrial competitiveness [1]. One of the most notable is special publication (SP) 800-37 \u0026lsquo;Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy\u0026rsquo;. The target audience is any individual or organization associated with the design, development, implementation, assessment, operation, maintenance, and disposition of information systems [2]. This document provides a Risk Management Framework (RMF) for any information systems. Although designed for cyber risks, the framework applies as well to physical risks.\nSources are cited below, original article available free of charge here.\nPurpose of Publication Quoting the publication [2]:\n\u0026quot; The guidelines have been developed:\nTo ensure that managing system-related security and privacy risk is consistent with the mission and business objectives of the organization and risk management strategy established by the senior leadership through the risk executive (function); To achieve privacy protections for individuals and security protections for information and information systems through the implementation of appropriate risk response strategies; To support consistent, informed, and ongoing authorization decisions, reciprocity, and the transparency and traceability of security and privacy information; To facilitate the integration of security and privacy requirements and controls into the enterprise architecture, SDLC processes, acquisition processes, and systems engineering processes; To facilitate the implementation of the Framework for Improving Critical Infrastructure Cybersecurity [NIST CSF] within federal agencies. \u0026quot; This publication provides means for handling organizational risks to information systems. Establishing rules for data privacy, data owners, data transparency, and secure software development. The focus is on a framework for addressing, understanding, mitigating, and accepting risk. It provides no specific countermeasures for risks instead focusing at the organization level.\nFundamentals and the Risk Management Process This publication takes a three tiered approach to managing risk as demonstrated in the following diagram [2]:\nSummarizing figure 1:\nOrganization This tier focuses on governance and program-related risk management [1]. Preparing the organization to execute the RMF [3]. Here, important decisions linked to the business objectives, system modernization, enterprise architecture, and resource allocation are made. The primary responsibilities are: to understand risk, to assign roles, to identify critical functions, and to prioritize security requirements. Mission/Business Process This level focuses on the business or mission objectives. Such as defining the criticality of information flow between the organization and its partners [1]. Although related to level one, the focus is information flow, communication, and assigning task criticality. Information System This level defines the risk to information technology. Where risk to physical and digital information becomes less organizational and more practical. Communication of risks and priorities flow down the diagram. Incident reporting flows up. Feedback is provided from the information system level to the organization level. Ensuring every keyholder is up to date on the critical threats. New directives and priorities will flow down. Returning to the information system level. Once careful consideration of the reports and threat intelligence collected adn analyzed.\nOnce a conceptualization of the framework is understood, stakeholders should execute the process. The NIST RMF isolates seven key steps to ensure that activities are successfully executed [2]:\nPrepare Both organization and system level preparation is needed to establish a context and priorities for managing security and privacy risks. Categorize The system and information processed, stored, and transmitted should be categorized based on the impact of loss. Select Select an initial set of controls and tailor the controls as needed to reduce risk to an acceptable and manageable level. Implement Implement the controls and document thoroughly. Assess Determine if all controls are implemented correctly, operating as intended, and producing desirable outcomes. Authorize Authorize system controls based on a risk assessment. Monitor Monitor control efficaciousness, perform ongoing maintenance, and document all changes, assessments, feedback, and analysis. The publication provides further insight into each step. Including the smallest set of required tasks for full implementation of each step. Providing critical information on potential inputs, executed outputs, and the primary role responsible. Reviewing this set of tasks and covering the enumerated risk is essential. Any team or organization will gain from this type of review.\nConclusion The RMF provides more than the fundamentals for organizational risk management. Including supply chain risk management, security and privacy, authorization boundaries, and more. Understanding the full conceptual framework for determining and addressing risk is critical. NIST RMF is by no means a one size fits all solution to risk management. Only a framework that highlights common risks and strategies used in the field. This publication provides crucial insight into any organization\u0026rsquo;s information infrastructure and data security.\nSources B. Chapman and F. Maymi, CompTIA CySA+ cybersecurity analyst certification all-in-one exam guide, second edition (exam CS0-002), 2nd ed. Columbus, OH: McGraw-Hill Education, 2020. Joint Task Force Transformation Initiative, “Risk management framework for information systems and organizations: A system life cycle approach for security and privacy,” National Institute of Standards and Technology, Gaithersburg, MD, 2018. Acronym Dictionary NIST: National Institute of Standards and Technology RMF: Risk Management Framework SP: Special Publication\nCopyright Notice Copyright © 2024 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/nist_sp_800-37/","summary":"NIST SP800-37 Risk Management Framework summary.","title":"NIST SP800-37 Risk Management Framework"},{"content":"CIA and DAD Triads The CIA and DAD describe the essential objectives and threats to a system. Although created for cyberspace, these concepts apply to physical security too.\nThe CIA triad describes objectives in securing a system: Confidentiality, Integrity, and Availability. Each of the three affects the other two in equal measure. A system cannot be available if the infrastructure lacks integrity. Further, if accessible to no one, then it is not confidential as the information is unusable. Still, it is often useful to consider each of the concepts on its own.\nConfidentiality is important when considering access to data. Limiting access to the smallest group of users is essential. For each user provided access, the threat grows exponentially.\nIntegrity refers to the structure of the system itself. The infrastructure surrounding a system determines its safety and security. This encompasses both man-made and natural threats. Hardware compromised by a natural disaster is unavailable to use. This can be as damaging as a threat actor leaking internal data.\nFinally, availability concerns the uptime of a system. In mission-critical environments, the system must be available 24/7. Every year, developers transition critical systems over to web applications. Cloud providers host most of these applications and provide critical security infrastructure. Their primary focus is on maintaining the availability of the system for their users.\nThe DAD triad inverses the CIA triad describing the threats against a system. These are disclosure, alteration, and denial. Each of these is the threat to the corresponding member of the CIA triad. Disclosure threatens confidentiality, alteration threatens integrity, and denial threatens availability. This direct mapping provides a convenient tool for threat modeling.\nCombining members of the CIA and DAD triads yields helpful questions. For instance, \u0026ldquo;does the public server have access to disclose confidential information?\u0026rdquo; Using this method, potential threat vectors are obvious. A public server should not have access to any confidential data as that increases risk. Now, the next action item for the security team is clear - isolate the public interfaces.\nThese triads are guidelines rather than rigid categories. Most objectives and threats will fall into all the categories. Consider a DDoS attack, it jeopardizes availability and integrity immediately. With the integrity compromised, security measures may fail leading to unauthorized data access. Compromising all three members of the CIA triad. By considering each member on its own, the mitigation of the threat becomes more obvious. A solution like Cloudflare may further improve availability. Hardening encryption of the data on the protected server improves confidentiality. Adding a redundant server improves integrity. All three measures are clear goals and together reduce the threat.\nThe CIA and DAD triads form the backbone of modern security and threat modeling.\nSources M. Chapple and D. Seidl, CompTIA security+ study guide: Exam SY0-601, 8th ed. Indianapolis, IN: Sybex, 2021.\nCopyright Notice Copyright © 2024 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/triads/","summary":"Overview of the CIA and DAD triads.","title":"CIA and DAD Triads"},{"content":"Postulates - Assumptions Euclid\u0026rsquo;s postulates are a set of assumptions that describe geometry. These postulates are the smallest necessary set of assumptions required for Euclid\u0026rsquo;s proofs.\nPostulates (Assumptions):\nTo draw a straight line from any point to any point A finite straight line is a line between any two points To produce a finite straight line continuous in a straight line A finite continuous straight line exists To Describe a circle with any center and distance A circle can exist with any radius That, if a straight lines falling on two straight lines make the interior angles on the same side less than two right angles, the two straight lines, if produced indefinitely, meet on that side which are the angles less than the two right angles Two skewed lines will intersect on the side where the angle is acute. Notions - Axioms Notions are axioms for Euclid\u0026rsquo;s Elements. These axioms do not match modern geometry. Modern axioms encompass all assumptions made by Euclid in a different form. Allowing for all Euclid\u0026rsquo;s proofs to remain valid while expanding their scope. Some interpretations of Euclid cite more notions. Only the following four are the necessary set.\nAxioms provide the boundaries of the universe in which any theorems are true. Euclid proved several properties of lines and angles within these boundaries. When boundaries change, the truth of the theorem does as well. In modern math, we separate geometry into the Euclidian and non-Euclidian spaces. Euclid\u0026rsquo;s theorems are all truth on a flat 2D plane. Changing the boundaries allows the plane to bend in three dimensions. Drawing parallel lines on a bending plane may lead to an intersection. Violating many core theorems of Euclidean geometry. Anything that changes the boundary conditions may change the truth of the statement.\nNotions (Axioms):\nThings which are equal to the same thing are also equal to one another Transitive property applies to geometry. If two triangles are equal to the same triangle, then they are equal. If A = B and B = C, then A = C If equals be added to equals, the wholes are equal Euclid\u0026rsquo;s statement applies to geometry. That is two lines create a line and two rectangles added will create a rectangle. If equals be subtracted from equals, the remainders are equal Subtracting a rectangle from a rectangle leaves a rectangle. Subtracting an angle from an angle leaves an angle. Things which coincide with one another are equal to one another Two angles of equal pairs of lines are equal. The whole is greater than the part If A + B = C, then C \u0026gt; A and C \u0026gt; B. Again, consider the application is geometry so both A and B are non-zero or existent geometry. Sources Euclid, Euclid’s Elements. Santa Fe, NM: Green Lion Press, 2002.\nCopyright Notice Copyright © 2024 by Cassandra Pearson. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law.\nAI Training Notice I do not consent to have my work used for training AI. No portion of this work may be used for training artificial intelligence without written permission.\n","permalink":"https://pearsonify.github.io/posts/euclid_postulates/","summary":"Euclid\u0026rsquo;s axioms and postulates from the elements.","title":"Euclid's Postulates"}]