empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 00:45:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Articles: Fix broken links (#11427)

Browse Source 
Changes:
- Updated broken links in three Markdown articles.
This commit is contained in:
Eric 2023-04-28 13:55:54 -05:00 committed by GitHub
parent 47f96fe396
commit 7aeb1894be
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
articles/fleet-3.5.0.md
View File

@ -35,7 +35,7 @@ In the prior 3.4.0 release, we introduced the fleetctl preview command which all
In 3.5.0, we’ve added new messaging to appear while you wait for the instance to start and we’ve reduced the waiting time. In 3.5.0, we’ve added new messaging to appear while you wait for the instance to start and we’ve reduced the waiting time.
With the fleetctl preview command, a user can download and start a collection of resources useful for setting up a test environment with osquery, Fleet, and an ELK stack. Check out [github.com/fleetdm/osquery-in-a-box](github.com/fleetdm/osquery-in-a-box) for more details. With the fleetctl preview command, a user can download and start a collection of resources useful for setting up a test environment with osquery, Fleet, and an ELK stack. Check out [github.com/fleetdm/osquery-in-a-box](https://github.com/fleetdm/osquery-in-a-box) for more details.
--- ---

2
articles/tales-from-fleet-security-securing-the-startup.md
View File

@ -65,7 +65,7 @@ We will keep trying the same approach in every country where we need Macs, thoug
We adapted our onboarding procedures. We ordered laptops as soon as possible in the hiring process, but that was not enough since delays often take 4 to 8 weeks. Nothing would be more depressing for a new Fleetie than starting their new job and not being able to work for a few weeks. As someone who has suffered that pain many times before, I never would inflict it on someone else! We adapted our onboarding procedures. We ordered laptops as soon as possible in the hiring process, but that was not enough since delays often take 4 to 8 weeks. Nothing would be more depressing for a new Fleetie than starting their new job and not being able to work for a few weeks. As someone who has suffered that pain many times before, I never would inflict it on someone else!
We configured our SaaS tools and developed [a strategy](https://fleetdm.com/use-cases/apply-byod-to-soothe-supply-chain-pain) that would allow people to work from personal devices while limiting the risk. As we grow and our exposure changes, we will keep rebalancing this strategy so new hires can be productive before receiving a company-owned laptop. We configured our SaaS tools and developed [a strategy](https://fleetdm.com/securing/apply-byod-to-soothe-supply-chain-pain) that would allow people to work from personal devices while limiting the risk. As we grow and our exposure changes, we will keep rebalancing this strategy so new hires can be productive before receiving a company-owned laptop.
### Secure Configuration ### Secure Configuration

2
articles/tales-from-fleet-security-soc2.md
View File

@ -43,7 +43,7 @@ One of the essential things about SOC 2 is having the right security policies. T
Writing policies from scratch can seem daunting. Many compliance automation products have templates you can use to get started, but there are excellent free and open resources online. Writing policies from scratch can seem daunting. Many compliance automation products have templates you can use to get started, but there are excellent free and open resources online.
As you can see, our policies are in our [handbook](https://fleetdm.com/handbook/security-policies#information-security-policy-and-acceptable-use-policy), and we created most of them using this [free set of templates](https://github.com/JupiterOne/security-policy-templates) published by JupiterOne under Creative Commons licensing. As you can see, our policies are in our [handbook](https://fleetdm.com/handbook/business-operations/security-policies#information-security-policy-and-acceptable-use-policy), and we created most of them using this [free set of templates](https://github.com/JupiterOne/security-policy-templates) published by JupiterOne under Creative Commons licensing.
We kept our policies as basic as possible to make sure everything in them is valuable and achievable. Having policies that state you must do the impossible is a surefire way of getting in trouble! The templates we used contained many processes and procedures as well. We used the policies and will eventually document more of our procedures in our handbook. We kept our policies as basic as possible to make sure everything in them is valuable and achievable. Having policies that state you must do the impossible is a surefire way of getting in trouble! The templates we used contained many processes and procedures as well. We used the policies and will eventually document more of our procedures in our handbook.