Website upgrade #2
Loading…
Reference in New Issue
No description provided.
Delete Branch "facelift"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@ -0,0 +12,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h2>Understand and mitigate security threats others won't see coming.</h2>
<p>We believe security compromises to your systems and personnel are <b>inevitable</b>. Allow our team of expert technologists to help you reduce the likelihood and impact of security risks by thinking from first principles.</p>
I don't want to ever use the word expert to describe ourselves.
I prefer "experienced security engineers" and then we can change "security risks" to just "risks" since we just used the word security so it is implied.
@ -0,0 +29,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h2>We help secure the industry leaders.</h2>
<p>Some of the most sophisticated and sensitive systems in the industry have benefited from Distrust helping ensure that they are properly secured. Our clients see us as someone who will help them catch risks that aren't on other firm's radars.</p>
We already said "catch the risks others won't see coming" earlier so this reads as repetitive.
How about:
"We specialize in working with high risk clients"
"If you protect valuable assets or data, or provide software to others that do, your adversaries will not play fair. We want to help you protect your team and remove single points of failure in your stack"
@ -0,0 +144,4 @@
<div class="text-well">
<h3>Security Assessment</h3>
<p>Holistic assessments of systems tailored to your needs. We leverage our in house expertise to analyze your system, thinking from first principles, in order to ensure its design, implementation and deployment all work coherently to establish a strong security posture.</p>
We offer full stack security assessments, covering anything that is in scope for a sophisticated adversary from compromising a third party library, bribing a devops engineer, or finding a oversight in your code. While we will point out specific flaws we find, we feel we offer the most value in helping you identify where you can make strategic improvements to your architecture to take entire classes of risk off the table.
@ -0,0 +153,4 @@
<div class="text-well">
<h3>Security Engineering</h3>
<p>Our team consists of engineers who are experts in a wide range of areas ranging across applied cryptography, HSMs, secure coding using languages such as rust and golang, quorum authentication, kernel hardening, CI/CD hardening and more. Leverage our experience to ensure your systems are secure by design, and use the best available architecture patterns.</p>
Again, I dislike self-selling ourselves as experts. If others want to call us that, we can't stop them, but it is not for us to claim.
We should always favor being conservative over salesy and our potential customers can see our work and decide for themselves if we have the required expert-ise.
How about:
"Our team is comprised security engineers with past lives as full time system administrators, and software engineers. We have extensive first hand experience in actually implementing custom security defenses for high risk organizations. We are happy to get as deep into the weeds planning new defense strategy as you like from Linux kernel hardening, to supply chain signing, to code quality and library choices."
@ -0,0 +162,4 @@
<div class="text-well">
<h3>Retained Security Support</h3>
<p>If you need additional security support, you can hire our team on retainer to have us available when you need us most. Our varied expertise allows us to assist you with a wide variety of security related challenges and activities.</p>
varied and variety feels repetitive. Let's reword
@ -0,0 +171,4 @@
<div class="text-well">
<h3>Research & Development</h3>
<p>Our team is active in both open source development and security research. We strive to build the tools that we feel will have the most impact on the overall security and privacy of internet users.</p>
Maybe something like:
"Rather than write the same document or tool 10 times and bill each client for it, we focus our unused retainer hours on open sourcing every document and tool we legally can, so we can focus our time with clients on their unique situations. If we are doing public work you would like so see more of, or that -almost- meets your needs, we would love to hear that and figure out a path to see your needs met."
@ -0,0 +13,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h2>How can we help you?</h2>
<p>Distrust offers a wide range of services which are tailored to your organization. Whether you need a complete security assessment, building a security program from scratch, or want to focus on assessing a specific aspect of your organization or system - we are here to help. Our experienced staff will work closely with you to understand your unique needs and create a tailor made solution that works for you.</p>
We want to avoid putting more proprietary code into the world. We can advise people on their private code, or write code that can be audited by anyone.
Maybe "building a security program from scratch" to "creating or improving an open source security tool"
@ -0,0 +49,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Security Engineering</h3>
<p>Our team consists of engineers who are experts in a wide range of areas ranging across applied cryptography, HSMs, secure coding using languages such as rust and golang, quorum authentication, kernel hardening, CI/CD hardening and more. Leverage our experience to ensure your systems are secure by design, and use the best available architecture patterns.</p>
Usual "expert" comment here
@ -0,0 +70,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Retained Security Support</h3>
<p>If you need additional security support, you can hire our team on retainer to have us available when you need us most. Our varied expertise allows us to assist you with a wide variety of security related challenges and activities.</p>
varied and variety in the same sentence, and sounds like a repeat of the same thing said elsewhere.
How about.
"We offer monthly retainer contracts to augment your existing security team with access to our combined experience as needed. You can drop questions to our team in a chat, or include is in security-relevant meetings as you like. Almost anything an in-house security team might do to protect your organization is in scope for us as well, including qualifying candidates, conducting interviews, reviewing code, evaluate third party risks, or be a security voice in the room when you are planning new products."
@ -0,0 +90,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Research & Development</h3>
<p>Our team is active in both open source development and security research. We strive to build the tools that we feel will have the most impact on overall security and privacy of internet users.</p>
maybe copy the blurb from the frontpage here as well
@ -0,0 +13,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h2>How can we help you?</h2>
<p>Distrust offers a wide range of services which are tailored to your organization. Whether you need a complete security assessment, want to create or improve an open source security tool, need a security built from scratch, or want to focus on assessing a specific aspect of your organization or system - we are here to help. Our experienced staff will work closely with you to understand your unique needs and create a tailor made solution that works for you.</p>
"need a security built from scratch" => "need security tooling tailored to your needs" ?
"from scratch" may imply we're not using or building atop existing tooling.
@ -0,0 +29,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Security Assessment</h3>
<p>Holistic assessments of systems tailored to your needs. We leverage our in house expertise to analyze your system, thinking from first principles, in order to ensure its design, implementation and deployment all work coherently to establish a strong security posture. The methodologies we leverage vary based on the context, and client needs.</p>
remove comma between "context, and client needs". only add comma after three items
@ -0,0 +49,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Security Engineering</h3>
<p>Our team consists of engineers who are experienced in a wide range of areas spanning across applied cryptography, HSMs, secure coding using languages such as rust and golang, quorum authentication, kernel hardening, CI/CD hardening and more. Leverage our experience to ensure your systems are secure by design, and use the best available architecture patterns.</p>
i would argue an oxford comma but i want to get this merged
@ -0,0 +70,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Retained Security Support</h3>
<p>We offer monthly retainer contracts to augment your existing security team with access to our combined experience as needed. You can drop questions to our team in a chat, or include is in security-relevant meetings as you like. Almost anything an in-house security team might do to protect your organization is in scope for us as well, including qualifying candidates, conducting interviews, reviewing code, evaluate third party risks, or be a security voice in the room when you are planning new products.</p>
"or include is in security-relevant meetings" ?
@ -0,0 +90,4 @@
<div class="flex-container-inner">
<div class="text-well">
<h3>Research & Development</h3>
<p>Rather than write the same document or tool 10 times and bill each client for it, we focus our unused retainer hours on open sourcing every document and tool we legally can, so we can focus our time with clients on their unique situations. If we are doing public work you would like so see more of, or that -almost- meets your needs, we would love to hear that and figure out a path to see your needs met.</p>
use proper emphasis:
<i>almost</i>
almost vs -almost-.Merged manually.
Pull request closed