mirror of
https://github.com/empayre/fleet.git
synced 2024-11-06 08:55:24 +00:00
Stay on course with your security compliance goals blog post (#6230)
* Stay on course with your security compliance goals blog post * Update stay-on-course-with-your-security-compliance-goals.md * Update stay-on-course-with-your-security-compliance-goals.md * Update articles/stay-on-course-with-your-security-compliance-goals.md Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Update articles/stay-on-course-with-your-security-compliance-goals.md Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Update articles/stay-on-course-with-your-security-compliance-goals.md Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Update articles/stay-on-course-with-your-security-compliance-goals.md Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Update articles/stay-on-course-with-your-security-compliance-goals.md Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Update stay-on-course-with-your-security-compliance-goals.md * Update stay-on-course-with-your-security-compliance-goals.md * Add cover for security compliance goals blog post * Adding cover image and metadata for cover * Update stay-on-course-with-your-security-compliance-goals.md I've added my revisions. I decided to keep the original headline to align with the image. Can you please take a look, @GuillaumeRoss? * Apply suggestions from code review Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> * Implementing Guillaume's suggestions Co-authored-by: Desmi-Dizney <99777687+Desmi-Dizney@users.noreply.github.com> Co-authored-by: Guillaume Ross <guillaume@fleetdm.com> Co-authored-by: Chris McGillicuddy <108031970+chris-mcgillicuddy@users.noreply.github.com>
This commit is contained in:
parent
733abe1aa7
commit
db253f915a
@ -0,0 +1,65 @@
|
||||
# Stay on course with your security compliance goals
|
||||
|
||||
![Security compliance goals](../website/assets/images/articles/security-compliance-goals-cover-800x450@2x.jpg)
|
||||
|
||||
Pursuing security compliance is a long journey. It isn’t so much taking a road trip as it’s setting sail on the open ocean. Regulatory changes can knock you off course. Learning new technology can take the wind out of your sails. And no matter how hard you try, you can never reach the horizon.
|
||||
|
||||
Are you feeling a little seasick? Don’t worry. There are ways to navigate the waters of security compliance and still enjoy smooth sailing.
|
||||
|
||||
We’ve explored how to [get and stay compliant](https://fleetdm.com/use-cases/get-and-stay-compliant-across-your-devices-with-fleet) before. In this article, we’ll walk through the steps you can take to measure progress toward compliance — and how Fleet can make this task more manageable.
|
||||
|
||||
## Set your goals
|
||||
|
||||
One of the reasons compliance is so complicated is that there isn’t a single set of rules. You have to determine what compliance means for your organization.
|
||||
|
||||
Are you creating internal processes and controls to stay secure? Is there a law or regulation required to do business? Which industry standards should you meet if you truly want to compete?
|
||||
|
||||
Answering questions like these is the first step to becoming compliant. After all, you can’t measure progress until you know where you’re going.
|
||||
|
||||
## Be realistic
|
||||
|
||||
Achieving the highest level of compliance for your industry is an admirable goal. But pursuing compliance perfection could tie up daily business operations.
|
||||
|
||||
For instance, if your organization has 30 employees who use MacBooks, it might be possible to make sure they all have the latest version of macOS installed. That goal gets more challenging to achieve as those MacBooks multiply to the hundreds or even thousands. In which case, you should focus on MacBooks accessing critical systems first. Then you can make sure most MacBooks across your organization are up to date within 30 days of a patch being released.
|
||||
|
||||
With scale comes complexity — especially for large companies. Different teams need different tools to get the job done. Databases must balance security with accessibility. Updating legacy platforms, when possible at all, could disrupt availability.
|
||||
|
||||
Holding so many people, teams, and departments to the highest security standards takes a lot of work. And, at the end of the day, you might just be getting in the way.
|
||||
|
||||
Be sure to set goals based on the resources you have available — and try not to let perfection stand in the way of progress.
|
||||
|
||||
## Limit the scope
|
||||
|
||||
While your industry probably has compliance standards, these recommendations may not apply to your entire organization.
|
||||
|
||||
Let’s look at the [Payment Card Industry Data Security Standard](https://www.pcisecuritystandards.org/) or PCI DSS. This is a set of standards that aims to protect credit card data against data theft and fraud. This is pretty important if your organization plans to accept card payments. But how many of your teams are in the position to collect payments — or even interact with customers?
|
||||
|
||||
There may be controls that apply to your entire company, like using multi-factor authentication. Security requirements like these make a real difference, and should be done even if you have no compliance requirement, but this isn’t always the case. Some guidelines either don't make sense for your business, or they don’t do much to actually improve security. Knowing which compliance standards apply to which teams and systems will help lighten the load across your organization, especially around audit season.
|
||||
|
||||
## Partner with technical experts
|
||||
|
||||
Ultimately, your Chief Information Security Officer, Head of Security or Chief Compliance Officer is responsible for ensuring compliance, depending on the structure of your organization. While security and compliance teams are often responsible for tracking compliance, they don't usually implement the controls on every platform. How could this scale?
|
||||
|
||||
Your company could hire more security specialists. Some organizations have thousands on staff, but we know this isn’t always a realistic option. The good news is that you don’t necessarily need more security and compliance people — just more people with security skills.
|
||||
|
||||
IT professionals and system administrators are in the perfect position to help you measure and improve compliance progress. They have the skills to keep your company’s devices secure. Applying those skills in time can be difficult. Make it easy for technical experts to see the compliance status of each system.
|
||||
|
||||
Now, your technical experts have more visibility. What should they do with it? If you explain the reasons behind compliance requirements, they can look for security issues proactively — and prevent concerns from becoming problems.
|
||||
|
||||
## Fleet makes tracking compliance easy
|
||||
|
||||
A little insight goes a long way. The right tools will take you even further. Fleet lets you create [policies](https://fleetdm.com/securing/what-are-fleet-policies) that ask questions about your devices — questions you can customize to meet your compliance goals. You can group these custom queries with [teams](https://fleetdm.com/docs/using-fleet/teams), eliminating unnecessary processes and lowering the level of effort for your organization.
|
||||
|
||||
If a device doesn’t comply with one of your policies, [Fleet can automatically create tickets in external systems](https://fleetdm.com/docs/using-fleet/automations#policy-automations) — so employees can fix the problem right away.
|
||||
|
||||
Fleet also lets you [assign users different levels of access](https://fleetdm.com/docs/using-fleet/permissions): Observer, Maintainer, and Admin. So, your CISO can create policies and assign them to different teams — preparing technical experts to run queries for up-to-the-minute data on devices. Though that might not be necessary. Fleet policies automatically refresh every hour.
|
||||
|
||||
Fleet policies, teams, and permissions empower employees at every level of your organization to share the responsibility of measuring compliance. With more hands on deck, going after your goals will be a breeze.
|
||||
|
||||
|
||||
<meta name="category" value="product">
|
||||
<meta name="authorFullName" value="Chris McGillicuddy">
|
||||
<meta name="authorGitHubUsername" value="fleetdm">
|
||||
<meta name="publishedOn" value="2022-06-14">
|
||||
<meta name="articleTitle" value="Stay on course with your security compliance goals">
|
||||
<meta name="articleImageUrl" value="../website/assets/images/articles/security-compliance-goals-cover-800x450@2x.jpg">
|
BIN
website/assets/images/articles/security-compliance-goals-cover-800x450@2x.jpg.jpg
vendored
Normal file
BIN
website/assets/images/articles/security-compliance-goals-cover-800x450@2x.jpg.jpg
vendored
Normal file
Binary file not shown.
After Width: | Height: | Size: 146 KiB |
Loading…
Reference in New Issue
Block a user