mGuard

# Architecture Details

This page is structured exactly by interactions.

## [[Producer Architecure|Producer Architecure]]

Data Adaptor

Attribute lookup table

Publisher

Queue Manager

Adaptor → Publisher → NAC-ABE → Repo → Manifest → PSync → Subscriber notified

NAC-ABE encryption

PSync Producer stuff 

Link to a detail page of NAC_ABE Usage

### Controller Internal Architecture

Access Manager

Policy Parser

Attribute-based DKEY issuance (black box: NAC-ABE authority)

Consumer → Controller → certificate validation → DKEY issuance → Consumer

### Consumer Internal Architecture

Subscriber

Subscription + stream list

Manifest updates (from PSync)

NAC_ABE COnsumer

Data + CK retrieval

Decryption pipeline (black box)

PSync → manifest fetch → data fetch → CK fetch → decryption → application callback

### Repository Role

Persistent store

Objects stored: data, CKs, manifests

### Sequence Diagrams

“Consumer receives new data in real time”

“DKEY request + issuance”

“Manifest publication pipeline”

![](old_system_design.png)

![](archi1.png)

### Message Sequence

![](msg_seq_diagram.png)