-
Notifications
You must be signed in to change notification settings - Fork 0
/
what_I_am_doing.txt
41 lines (21 loc) · 1.52 KB
/
what_I_am_doing.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Sure, I'm happy to provide more details and expand on the proposed compliance monitoring solution:
**Data Ingestion**
- Build adapters and parsers to handle ingestion of varied log data formats - text, CSV, database logs etc.
- Support common protocols like Syslog, SNMP, FTP for streaming log collection
- Normalize and process raw logs into a schema suitable for compliance analysis
**LLM Training**
- Curate compliance corpus covering policies, regulations, controls
- Leverage transfer learning from existing models like Claude to speed up training
- Use techniques like prompt engineering to frame training in compliance context
- Continual learning as new policies get added to keep model updated
**Rule Extraction**
- Apply trained LLM model on new policy documents
- Extract compliance rules, requirements, constraints using classification and sequence labeling approaches
- Maintain lineage between original text and extracted rules
- Human validation of extracted rules before pushing to production
**Log Analysis**
- Build vector embeddings for normalized logs and rules
- Match logs to rules using semantic similarity measures like cosine distance
- Employ techniques like NER and relationship extraction to deeply analyze log context
- Generate structured violation records with associated log extracts and rule references
Let me know if you would like me to provide additional details on any specific components or aspects of the solution. I can extend this explanation further.