mirror of
https://github.com/Shiva108/ai-llm-red-team-handbook.git
synced 2026-10-13 19:21:05 +02:00
fix: adjust markdown code block fences and minor text formatting
This commit is contained in:
1 parent
c50979a222
commit
198cfb240c
3 files changed
+32
-32
No files matched your search
@@ -269,11 +269,11 @@ In AI red teaming, technical findings may have legal, business, or even social i
|
||||
|
||||
### Example: Reporting Table
|
||||
|
||||
| Audience | Communication Style | Example Message |
|
||||
| ---------------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Executive | Plain language, impact-focused | “Our tests found that anyone can access sensitive customer data in the chat logs, exposing us to GDPR fines.” |
|
||||
| Audience | Communication Style | Example Message |
|
||||
| ---------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Executive | Plain language, impact-focused | “Our tests found that anyone can access sensitive customer data in the chat logs, exposing us to GDPR fines.” |
|
||||
| Technical | Technical detail, steps, evidence | “Prompt injection via the ‘/support’ API bypasses intent filters - recommend input validation and stricter role separation.” |
|
||||
| Compliance/Legal | Documentation, traceability | “All model access was conducted using the provided test account and logs are attached as evidence.” |
|
||||
| Compliance/Legal | Documentation, traceability | “All model access was conducted using the provided test account and logs are attached as evidence.” |
|
||||
|
||||
## 2.6 Conflicts of Interest, Bias, and Fair Testing
|
||||
|
||||
@@ -12306,27 +12306,28 @@ Priority actions based on severity:
|
||||
# Example: Testing memorization on different models
|
||||
|
||||
MEMORIZATION_BENCHMARK = {
|
||||
'model': 'GPT-2-1.5B',
|
||||
'training_set_size': '40GB',
|
||||
'test_samples': 1000,
|
||||
'extraction_techniques': [
|
||||
'Direct completion',
|
||||
'Prefix-suffix attack',
|
||||
'Temperature manipulation'
|
||||
],
|
||||
'results': {
|
||||
'exact_matches': 127, # 12.7%
|
||||
'near_matches': 234, # 23.4%
|
||||
'partial_matches': 445, # 44.5%
|
||||
'no_match': 194 # 19.4%
|
||||
},
|
||||
'success_factors': [
|
||||
'Unique sequences: 85% extraction rate',
|
||||
'Common sequences: 15% extraction rate',
|
||||
'Repeated data: 95% extraction rate'
|
||||
]
|
||||
'model': 'GPT-2-1.5B',
|
||||
'training_set_size': '40GB',
|
||||
'test_samples': 1000,
|
||||
'extraction_techniques': [
|
||||
'Direct completion',
|
||||
'Prefix-suffix attack',
|
||||
'Temperature manipulation'
|
||||
],
|
||||
'results': {
|
||||
'exact_matches': 127, # 12.7%
|
||||
'near_matches': 234, # 23.4%
|
||||
'partial_matches': 445, # 44.5%
|
||||
'no_match': 194 # 19.4%
|
||||
},
|
||||
'success_factors': [
|
||||
'Unique sequences: 85% extraction rate',
|
||||
'Common sequences: 15% extraction rate',
|
||||
'Repeated data: 95% extraction rate'
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
````
|
||||
|
||||
**Success rates and methodologies**
|
||||
|
||||
@@ -12403,7 +12404,7 @@ MEMORIZATION_BENCHMARK = {
|
||||
3. Update controls based on new threats
|
||||
4. Regular penetration testing
|
||||
5. Continuous improvement
|
||||
```
|
||||
````
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||

|
||||
|
||||
# Chapter 2: Ethics, Legal, and Stakeholder Communication
|
||||
|
||||
S
|
||||
|
||||
## 2.1 Why Ethics Matter in AI Red Teaming
|
||||
|
||||
AI red teaming, by its very nature, grants you deep access to sensitive systems and data. With that access comes the responsibility to operate with integrity, professionalism, and a commitment to avoiding harm. Ethical lapses don’t just damage your reputation - they can put clients, end users, and even whole organizations at risk.
|
||||
@@ -80,11 +80,11 @@ In AI red teaming, technical findings may have legal, business, or even social i
|
||||
|
||||
### Example: Reporting Table
|
||||
|
||||
| Audience | Communication Style | Example Message |
|
||||
| ---------------- | --------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Executive | Plain language, impact-focused | “Our tests found that anyone can access sensitive customer data in the chat logs, exposing us to GDPR fines.” |
|
||||
| Audience | Communication Style | Example Message |
|
||||
| ---------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Executive | Plain language, impact-focused | “Our tests found that anyone can access sensitive customer data in the chat logs, exposing us to GDPR fines.” |
|
||||
| Technical | Technical detail, steps, evidence | “Prompt injection via the ‘/support’ API bypasses intent filters - recommend input validation and stricter role separation.” |
|
||||
| Compliance/Legal | Documentation, traceability | “All model access was conducted using the provided test account and logs are attached as evidence.” |
|
||||
| Compliance/Legal | Documentation, traceability | “All model access was conducted using the provided test account and logs are attached as evidence.” |
|
||||
|
||||
## 2.6 Conflicts of Interest, Bias, and Fair Testing
|
||||
|
||||
|
||||
@@ -1419,4 +1419,3 @@ RED_TEAM_BEST_PRACTICES = {
|
||||
**Key Takeaway**: Jailbreak research is essential for AI safety. Responsible testing, coordinated disclosure, and continuous improvement are critical for building robust, trustworthy AI systems.
|
||||
|
||||
---
|
||||
|
||||
Reference in new issue
Block a user