top of page

Rules of Engineering

Partner with End State Security, and experience services that are built on a solid foundation of engineering excellence and a commitment to safeguarding your digital assets. We adhere to a set of engineering principles that govern our approach to security.

While we prioritize client satisfaction, it's essential to acknowledge that certain requests may be unfeasible, some plans may be flawed, and certain designs won't effectively address the problem. In such situations, we strive to serve our clients by respectfully challenging and advocating for alternative solutions. Our ultimate objective is to solve problems without adding unnecessary complications or challenges for our clients.

Always take care of your clients

Rule One

Allow space for growth and ensure you incorporate an "other" category in all your sorting endeavors. Be prepared for worst-case scenarios, taking into account Murphy's Law and the General Uncertainty Principles. Neglecting these considerations may result in forced, unsatisfactory solutions, and even the tiniest decision can have significant repercussions in the future.

Allow for the unexpected

Rule Two

When facing criticism, modifications, or disregard towards your design, refrain from taking offense. Instead, embrace the opportunity to analyze alternative designs, learn from them, and discover better ways to solve the problem. Embracing this mindset will enable personal growth, expand your knowledge, and enhance your problem-solving abilities.

Keep your ego out of ideas

Rule Three

When encountering something unfamiliar or unverified, don't hesitate to speak up and seek clarification. Our reliance is on knowledge and factual information, not on speculation or assumptions. By promptly seeking understanding or confirmation, you can expedite the process of resolving our client's problems effectively.

Ask questions

Rule Four

Remain adaptable to the possibility of adjusting your plan based on new information, consistently exploring alternative approaches. Transparently share relevant facts with others, regardless of whether they align with or challenge your ideas. Recognize assumptions for what they are and actively seek to validate or invalidate them. Always double-check routing tables, ensure proper cable connections, and refrain from answering technical questions with uncertain statements. Instead, offer to confirm the information to ensure accuracy.

Work with facts and prepare alternatives

Rule Five

Opt for simplicity in solutions, as they are more manageable, comprehensible, and user-friendly. Whenever applicable, adhere to best practices, and when they don't apply, opt for the simplest and most straightforward solution. Ensure that names and configurations are accurate, clean, and self-explanatory. Whenever possible, remove legacy configurations to maintain a streamlined and efficient system.

Choose simple over complex

Rule Six

By default, technical information should be conveyed in writing to ensure clarity and accuracy. It is advisable to supplement significant verbal decisions or requests with follow-up emails. A written record surpasses the fleeting nature of sound waves and memories, providing a lasting reference and minimizing potential misunderstandings.

Communicate important information in writing

Rule Seven

Strive to prioritize signal over noise in your communications. Filling up conversations with speculation accomplishes nothing. Extraneous words can detract from the main point and create distractions. Keep your communications focused and concise.

Be concise

Rule Eight

Stay unwaveringly focused on the task at hand, disregarding distractions that may hinder progress. Maintain a steadfast commitment to problem-solving, to ensure efficient and effective resolutions.

Work the problem

Rule Nine

Memories fade, but notes are forever. Establish a robust system for identifying and tracking vital information, such as IP addresses, observed statistics, and implemented changes. These records serve multiple purposes: personal reference, collaboration with fellow engineers, and documentation. Time and again, your diligent note-taking will prove invaluable, potentially rescuing critical situations, both technical and non-technical.

Take notes

Rule Ten

When confronted with an unfamiliar situation, direct your attention towards what you already comprehend. If you encounter uncertainty in configuring certain features, prioritize executing the parts you are familiar with before addressing the unfamiliar aspects. This approach allows you valuable time to contemplate and strategize around the new problem, ensuring a thoughtful and well-informed resolution.

Focus on what you know

Rule Eleven

When escalating a problem to another engineer, it is crucial to provide clear communication regarding the steps you have taken and those you haven't. Proactively share relevant credentials, IP addresses, and other pertinent information without waiting for the other party to inquire. While offering ideas, guesses, and suggestions, it is essential to explicitly label them as such, ensuring transparency and open collaboration.

Escalate with facts

Rule Twelve

Rules of Engineering

Contact End State Security Today

bottom of page