> For the complete documentation index, see [llms.txt](https://management.lunr.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://management.lunr.tech/how-we-ensure-peoples-growth/compensation/ic-frameworks/information-security.md).

# Information security

LUNR is rapidly expanding. Our teams are in continuous motion, and we’re constantly welcoming new people to join our company. The Information Security team needs to keep up with this fast-changing environment and ensure that our company's data is protected by ensuring that all parties have the right access to work safely.

It's also under the responsibility of the Information Security team to manage the security of our network and servers, monitor activities, establish compliant procedures, and guarantee the protection of our datacenter.

Advancing in this framework consists of being on the lookout for new threats and finding new ways of safeguarding our company through effective management of processes, methodologies, costs, and policies assuring LUNR's ability to function and grow as an ethical, compliant, and transparent organization.

## Progression

In order to progress in our development path and Level Up or Step Up, our security guys developers must:

* Meet the criteria of the Level & Step Chart for the [Individual Contributors Path](#user-content-fn-1)[^1]
* Meet the [KAI ](/how-we-build-processes-and-a-great-product/knowledge-management/knowledge-accountability-index.md)grade of the framework related to each level
* Demonstrate proficiency in LUNR knowledge

### Salary Grid

All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.

| Information Security        | Step  |       |       |       |
| --------------------------- | ----- | ----- | ----- | ----- |
| Level                       |       |       |       |       |
| Individual Contributor Path | 1     | 2     | 3     | 4     |
| 1                           | 4.160 | 4.310 | 4.466 | 4.610 |
| 2                           | 5.160 | 5.310 | 5.466 | 5.610 |
| 3                           | 6.160 | 6.310 | 6.466 | 6.610 |
| 4                           | 7.160 | 7.310 | 7.466 | 7.610 |
| 5                           | 8.160 | 8.310 | 8.466 | 8.610 |
| 6                           | 9.160 | 9.310 | 9.466 | 9.610 |

### [KAI ](/how-we-build-processes-and-a-great-product/knowledge-management/knowledge-accountability-index.md)of the framework

Extensive knowledge

<figure><img src="/files/cJklozNN6D7y1yLbTZKi" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/g7Tdc48zpnAZHjYIYR5S" alt=""><figcaption></figcaption></figure>

[^1]:


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://management.lunr.tech/how-we-ensure-peoples-growth/compensation/ic-frameworks/information-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
