> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/patch-management-protocols.md).

# Patch Management Protocols

Patch management is a crucial process that involves keeping software and systems up to date in order to address known vulnerabilities. It involves regularly applying patches, updates, and fixes to software and operating systems to ensure their security and stability.\
\
By keeping software and systems up to date, Flosum effectively mitigates the risk of potential security breaches and cyberattacks. Patch management helps to address known vulnerabilities by closing security loopholes and fixing bugs that could be exploited by malicious actors.\
\
Flosum’s patch management strategy includes regularly monitoring for available patches, testing them in a controlled environment, and deploying them across the organization's infrastructure, as well as:

1. A risk-informed systems patch cycle for all server operating systems (OS) shall be scheduled, as appropriate, for Information Systems and related subsystems.
2. Any emergency patching outside of the routine patching schedule shall be done according to level of risk, as determined by the Information System Owner in consultation with the CISO.
3. Servers, services, or applications shall be maintained with current OS, application, or security patch levels, as recommended by the software manufacturer and informed by risk, to protect Flosum Information from known information security issues.

In addition to addressing security vulnerabilities, our patch management also plays a vital role in maintaining system performance and reliability. Software updates often include performance enhancements and bug fixes, which can result in improved functionality and reduced system downtime.\
\
Overall, patch management is an essential practice to proactively protect our software and systems from potential threats. By keeping software up to date, we maintain a secure and resilient IT environment.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/resources/policies-and-security/corporate-policies-and-security-compliance/product-level-certifications/backup-and-archive/flosum-backup-and-archive-security-and-compliance-statement/patch-management-protocols.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.