> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/how-to/live-cyber-attack-simulation/data-corruption.md).
# Data corruption
Data corruption is the **alteration of data in a way that it becomes incorrect, inconsistent, or unusable**. It's a way of seeing if someone is potentially tampering with your website or some of your backend is being manipulated. This can be simulated in Conducttr using smartwords.
There are four steps to take to simulate data corruption:
1. Set up your inject and smartwords in the MEL
2. Modify smartwords during the exercise
3. Re-publish the inject
4. Check the inject in the player view
{% stepper %}
{% step %}
### Set up: Inject and Smartword
#### Inject
Create an inject containing a Smartword.
Smartword
In Configuration > Smartwords set up your text. Once completed, remember to upload to your space.
{% endstep %}
{% step %}
### Modify in the Facilitator Dashboard
While running the exercise in the Facilitator Dashboard, navigate to `Content` > `Smartwords` and change the text. Once finished, click `Update data`.
{% endstep %}
{% step %}
### Re-publish the inject
Smartwords are not retroactive so it doesn't go back and change what has already been published, hence we have to re-publish the article again.
There are two ways to re-publish the inject:
1. Publish to player
2. Pre-planned inject
#### Publish to player
Publish the article again by navigating to the scenario editor, right-clicking on the inject and then `Publish to player`:
#### Pre-planned inject
Or, you can plan an inject with the same smartword to appear later on in the exercise. This will re-publish the news article with the updated smartword.
This option isn't as flexible as the one above since it's timed. If you go with this method, it's a good idea to also add a notification for the Facilitator to change the smartword.
{% endstep %}
{% step %}
### Check the player view
The example below shoes the website working with the new Smartword:
{% endstep %}
{% endstepper %}
---
# 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://helpdocs.conducttr.com/how-to/live-cyber-attack-simulation/data-corruption.md?ask=&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.
