You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 4, 2026. It is now read-only.
The Compass Security fork includes fixes and new features!
137
130
138
-
We would love to hear back from you, if something is broken or have and idea to make it better add a ticket or connect to us on the [PurpleOps Discord](https://discord.gg/2xeA6FB3GJ) or email us at pops@purpleops.app | `@_w_m__`
131
+
### Updated Dependencies
132
+
The Python dependencies (e.g. Flask) were updated to the latest versions.
139
133
140
-
## Credits
134
+
### Restructured Test Case Form and Flow-Based Approach
135
+
We have redesigned the test case form to prioritise the elements that we believe are important during a purple team engagement.
136
+
<br> Is there anything missing? Please let us know — we are eager to hear how other analysts approach Purple Teaming engagements.
137
+
138
+
<br>Moreover, we have implemented a flow-based approach to facilitate collaboration with the Blue Team.
This signals to the blue team that input is expected from their side. Once the required information has been added, the Blue team can set the state to 'Waiting Red'.
143
+
Users with the 'Blue' role can only edit a test case if it is in the 'Waiting Blue' or 'Waiting Red' state.
144
+
145
+
#### Waiting Red:
146
+
This signals to the red team that the blue team has finished adding their details to the test case. The red team can then check that all the required information is present. If so, the state can be changed to 'Complete'.
147
+
148
+
#### Complete:
149
+
The blue team cannot make any more changes to the test case.
150
+
151
+
152
+
### Pytests
153
+
We have created pytests for each route. This makes it easy to check whether the application has been affected by any changes made to it.
154
+
<br><br>Note: We are still missing security checks (e.g. RBAC) and application logic checks, so if you would like to contribute, we would be glad to merge your pull request!
155
+
156
+
### Dark Mode
157
+
Enjoy PurpleOps in dark mode. To enable this, go to the settings menu.
The Test Case History allows you to view previous saved versions of the test case. This feature is only available after an initial save, not after an import. Please note that evidence files are not stored.
The KB also enables you to set placeholders for frequently used strings. For instance, you could define {{TARGET_DOMAIN_USER}} as a placeholder in an MD file for a command.
177
+
```
178
+
net user {{TARGET_DOMAIN_USER}} /domain
179
+
```
180
+
Define a JSON file which contains all your placeholders and the coresponding text:
181
+
```
182
+
{
183
+
"DOMAIN_NAME" : "testlab.local",
184
+
"LOWPRIVILEGED_DOMAIN_USER" : "tmassie",
185
+
"TARGET_DOMAIN_USER" : "administrator",
186
+
"DC_IP" : "10.0.1.10"
187
+
}
188
+
```
189
+
Upload the JSON file to PurpleOps using your browser. The values will be stored in your session storage (cleared after browser is closed). Use the toggle in the test case KB to replace the placeholders with real data.
0 commit comments