Update README.md
Browse files
README.md
CHANGED
@@ -21,49 +21,42 @@ This model card aims to document the capabilities, performance, and intended usa
|
|
21 |
## Model Details
|
22 |
|
23 |
### Model Description
|
24 |
-
|
25 |
This model is a fine-tuned version of large-scale language models optimized for tasks such as parsing shell commands and analyzing cybersecurity exploits. The training leverages datasets such as Canstralian/ShellCommands and Canstralian/CyberExploitDB to provide domain-specific knowledge.
|
26 |
|
27 |
-
|
28 |
-
|
29 |
-
|
30 |
-
|
31 |
-
|
32 |
-
|
33 |
-
## Uses
|
34 |
|
35 |
-
###
|
36 |
|
|
|
37 |
The model is intended to be used directly for tasks like:
|
38 |
- Shell command understanding and classification
|
39 |
- Analyzing and classifying cybersecurity exploit patterns
|
40 |
- Assisting with code generation and debugging in a cybersecurity context
|
41 |
|
42 |
-
|
43 |
-
|
44 |
When fine-tuned further, the model can be applied to:
|
45 |
- Automated incident response systems
|
46 |
- Security tool integration (e.g., for vulnerability scanners)
|
47 |
- Custom cybersecurity solutions tailored to enterprise needs
|
48 |
|
49 |
-
|
50 |
-
|
51 |
The model is not designed for general-purpose natural language understanding outside of its specified cybersecurity domain. It may perform poorly or inaccurately for tasks outside of:
|
52 |
- Shell command parsing
|
53 |
- Exploit database analysis
|
54 |
- Code generation for cybersecurity applications
|
55 |
|
56 |
-
|
57 |
-
|
58 |
This model may exhibit bias in the detection of certain exploits or shell commands, particularly if it encounters unfamiliar patterns not covered in the training data. Additionally, the model's predictions may be less accurate on unseen datasets or with edge cases that were not represented in the training data.
|
59 |
|
60 |
### Recommendations
|
61 |
-
|
62 |
- Users should be cautious when applying the model to novel or unverified exploits, as it may not handle new attack vectors well.
|
63 |
- Regular evaluation and testing in real-world environments are recommended before deploying the model in production.
|
64 |
|
65 |
-
|
66 |
-
|
67 |
Use the code below to get started with the model:
|
68 |
|
69 |
```python
|
@@ -76,84 +69,4 @@ nlp = pipeline("text-classification", model=model_name)
|
|
76 |
# Example usage
|
77 |
result = nlp("Example shell command or exploit input")
|
78 |
print(result)
|
79 |
-
```
|
80 |
-
|
81 |
-
## Training Details
|
82 |
-
|
83 |
-
### Training Data
|
84 |
-
|
85 |
-
The model was fine-tuned on the following datasets:
|
86 |
-
- **Canstralian/ShellCommands**: A collection of shell commands used in cybersecurity contexts.
|
87 |
-
- **Canstralian/CyberExploitDB**: A curated set of known exploits and vulnerabilities.
|
88 |
-
|
89 |
-
Further details on the preprocessing of these datasets can be found in their respective dataset cards.
|
90 |
-
|
91 |
-
### Training Procedure
|
92 |
-
|
93 |
-
#### Preprocessing
|
94 |
-
|
95 |
-
The data was preprocessed to remove any sensitive or personally identifiable information. Text normalization and tokenization were applied to ensure consistency across the datasets.
|
96 |
-
|
97 |
-
#### Training Hyperparameters
|
98 |
-
|
99 |
-
- **Training regime:** fp16 mixed precision
|
100 |
-
|
101 |
-
## Evaluation
|
102 |
-
|
103 |
-
### Testing Data, Factors & Metrics
|
104 |
-
|
105 |
-
#### Testing Data
|
106 |
-
|
107 |
-
Testing was performed on both synthetic and real-world shell command and exploit datasets, focusing on their ability to correctly parse shell commands and identify exploit signatures.
|
108 |
-
|
109 |
-
#### Factors
|
110 |
-
|
111 |
-
The evaluation factors included:
|
112 |
-
- Model performance across different types of shell commands and exploits.
|
113 |
-
- Accuracy, precision, recall, and F1-score in detecting known exploits.
|
114 |
-
|
115 |
-
#### Metrics
|
116 |
-
|
117 |
-
Metrics used for evaluation include:
|
118 |
-
- **Accuracy**: Percentage of correct predictions made by the model.
|
119 |
-
- **Precision**: The number of relevant instances among the retrieved instances.
|
120 |
-
- **Recall**: The number of relevant instances that were retrieved.
|
121 |
-
- **F1-score**: The harmonic mean of precision and recall.
|
122 |
-
|
123 |
-
### Results
|
124 |
-
|
125 |
-
The model performs well on standard shell command parsing tasks and exploit detection, with high accuracy for common exploits. However, its performance may degrade on newer or less common exploits.
|
126 |
-
|
127 |
-
#### Summary
|
128 |
-
|
129 |
-
The model is well-suited for cybersecurity applications involving shell command and exploit detection. While it excels in these areas, users should monitor its performance for emerging threats and unusual attack patterns.
|
130 |
-
|
131 |
-
## Model Examination [optional]
|
132 |
-
|
133 |
-
Relevant interpretability work for this model is ongoing. Future research will focus on understanding why the model makes specific predictions and improving its interpretability.
|
134 |
-
|
135 |
-
## Environmental Impact
|
136 |
-
|
137 |
-
Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
|
138 |
-
|
139 |
-
- **Hardware Type:** [More Information Needed]
|
140 |
-
- **Hours used:** [More Information Needed]
|
141 |
-
- **Cloud Provider:** [More Information Needed]
|
142 |
-
- **Compute Region:** [More Information Needed]
|
143 |
-
- **Carbon Emitted:** [More Information Needed]
|
144 |
-
|
145 |
-
## Glossary [optional]
|
146 |
-
|
147 |
-
Terms like "shell command", "exploit", and "cybersecurity" may be used frequently in this model's context. Further definitions will help readers understand model performance.
|
148 |
-
|
149 |
-
## More Information [optional]
|
150 |
-
|
151 |
-
[More Information Needed]
|
152 |
-
|
153 |
-
## Model Card Authors [optional]
|
154 |
-
|
155 |
-
[More Information Needed]
|
156 |
-
|
157 |
-
## Model Card Contact
|
158 |
-
|
159 |
-
For more information, please contact [Contact Information Needed].
|
|
|
21 |
## Model Details
|
22 |
|
23 |
### Model Description
|
|
|
24 |
This model is a fine-tuned version of large-scale language models optimized for tasks such as parsing shell commands and analyzing cybersecurity exploits. The training leverages datasets such as Canstralian/ShellCommands and Canstralian/CyberExploitDB to provide domain-specific knowledge.
|
25 |
|
26 |
+
**Developed by**: Canstralian
|
27 |
+
**Model type**: Transformer-based Language Model for cybersecurity applications
|
28 |
+
**Language(s) (NLP)**: English (en)
|
29 |
+
**License**: MIT
|
30 |
+
**Finetuned from model**: WhiteRabbitNeo/WhiteRabbitNeo-13B-v1, replit/replit-code-v1_5-3b
|
|
|
|
|
31 |
|
32 |
+
### Uses
|
33 |
|
34 |
+
#### Direct Use
|
35 |
The model is intended to be used directly for tasks like:
|
36 |
- Shell command understanding and classification
|
37 |
- Analyzing and classifying cybersecurity exploit patterns
|
38 |
- Assisting with code generation and debugging in a cybersecurity context
|
39 |
|
40 |
+
#### Downstream Use
|
|
|
41 |
When fine-tuned further, the model can be applied to:
|
42 |
- Automated incident response systems
|
43 |
- Security tool integration (e.g., for vulnerability scanners)
|
44 |
- Custom cybersecurity solutions tailored to enterprise needs
|
45 |
|
46 |
+
#### Out-of-Scope Use
|
|
|
47 |
The model is not designed for general-purpose natural language understanding outside of its specified cybersecurity domain. It may perform poorly or inaccurately for tasks outside of:
|
48 |
- Shell command parsing
|
49 |
- Exploit database analysis
|
50 |
- Code generation for cybersecurity applications
|
51 |
|
52 |
+
### Bias, Risks, and Limitations
|
|
|
53 |
This model may exhibit bias in the detection of certain exploits or shell commands, particularly if it encounters unfamiliar patterns not covered in the training data. Additionally, the model's predictions may be less accurate on unseen datasets or with edge cases that were not represented in the training data.
|
54 |
|
55 |
### Recommendations
|
|
|
56 |
- Users should be cautious when applying the model to novel or unverified exploits, as it may not handle new attack vectors well.
|
57 |
- Regular evaluation and testing in real-world environments are recommended before deploying the model in production.
|
58 |
|
59 |
+
### How to Get Started with the Model
|
|
|
60 |
Use the code below to get started with the model:
|
61 |
|
62 |
```python
|
|
|
69 |
# Example usage
|
70 |
result = nlp("Example shell command or exploit input")
|
71 |
print(result)
|
72 |
+
```
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|