Can corporate security teams audit Oyma's network traffic and code?

Open Verification for Enterprise Procurement

Enterprise InfoSec teams face significant hurdles when evaluating modern AI productivity software: third-party cloud architectures, opaque data-sharing pipelines, and non-negotiable telemetry tracking.

Oyma is built from the ground up to facilitate frictionless technical auditing by corporate security engineers.

1. Network Traffic Auditing

Security engineers can place a workstation running Oyma behind an active network proxy or packet sniffer:

• Little Snitch / LuLu Rules: Create a strict firewall rule blocking all outbound connections from Oyma. In local mode, Oyma continues functioning at 100% capability with zero alert popups.
• Wireshark Packet Analysis: Capture promiscuous network traffic while recording calls and running Whisper transcription. The packet capture stream confirms zero outbound DNS, TCP, or UDP packets.

# Capture network packets specifically while running Oyma
sudo tcpdump -i en0 -nn -s0 -w audit_capture.pcap

2. Binary Code Signature & Hardened Runtime

Every release of Oyma is cryptographically signed with an official Apple Developer ID certificate and packaged under Apple’s Hardened Runtime environment:

# Verify Apple Developer ID signature and integrity
codesign -dv --verbose=4 /Applications/Oyma.app
spctl --assess --type execute --verbose /Applications/Oyma.app

This ensures that the binary has not been tampered with, contains no unauthorized dynamic libraries, and satisfies macOS execution integrity policies.

3. File Access Auditing

Using native macOS fs_usage, security auditors can inspect every disk read and write executed by the application:

sudo fs_usage -w -f filesys Oyma

Auditors can verify that Oyma accesses only the designated vault directory and its internal application support caches.

Corporate InfoSec Inspection and Verification Tools

Enabling technical verification by security administrators:

• Network Packet Capture: Monitor application traffic using Wireshark or tcpdump to confirm zero unauthorized transmissions.
• Binary Code Signatures: Inspect Apple Developer ID signatures and code execution integrity using codesign and spctl.
• Filesystem Access Monitoring: Track disk operations in real time using macOS fs_usage to verify directory boundaries.
• Firewall Rule Enforcement: Run Oyma under Little Snitch with outbound traffic completely blocked to verify full local functionality.

Full Administrative Auditability and Compliance

Security teams can verify binary signatures with codesign, monitor network silence with Little Snitch or Wireshark, and audit filesystem access boundaries using native macOS fs_usage tools.

IT administrators can also inspect the application bundle to verify that zero analytics SDKs or unauthorized third-party dynamic libraries are embedded in the software distribution.

Administrative Audit Checklist

• Network Monitoring: Inspect packet silence with Wireshark, Little Snitch, or tcpdump.
• Binary Verification: Validate Apple Developer ID signatures and code hardening using codesign.
• Filesystem Boundaries: Track real-time disk operations using macOS fs_usage to verify directory scoping.
• Code Hardening: Runs with Apple hardened runtime enabled and zero unsafe entitlements.