Nsasoft

Nsasoft specializes in delivering cutting-edge software solutions designed to monitor and secure IT environments and recover sensitive information.

[Nsasoft @NsasoftUS]

Every AI security scanner on the market ships your network telemetry to someone else’s cloud for inference.

NSAuditor AI Enterprise Edition runs AI inference locally. Zero Data Exfiltration. Air-gap ready.

https://t.co/JoRF2Sz6Bb

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.32.7 is live.

A security finding should mean the same thing in every framework it touches. Until now our network-scan agents routed to SOC 2 only — so a host serving cleartext could fail SOC 2 and read perfectly clean in the HIPAA, NIST, ISO, CIS, PCI & GDPR reports built from the *same scan*.

0.32.7 closes that gap. 🧵

[Diana @InvestWithD]

🚨UPDATE: Republicans and Democrats OFFICIALLY Meet TODAY to Finalize Clarity Act Ethics Deal 🤯🇺🇸

Republicans and Democrats are meeting TODAY to push the Clarity Act closer to the Senate floor, with negotiations entering what could be their MOST critical stage yet. 👀

Sources say discussions are focused on:

👉 Ethics provisions, which remain the BIGGEST obstacle to a final deal
👉 DeFi language, which is also still under active negotiation

Sen. @SenLummis says last week’s White House talks were “productive”. ✅

Text could be RELEASED SOON...

More updates to come.

[NSAuditor AI @Nsasoft]

A security scanner's worst failure is a clean verdict over a real exposure. NSAuditor AI 0.32.6 closes a cluster of those on the network-scan path — detection the tool should always have had. Matrix-neutral: no new framework, no coverage number moves. 🧵 #CyberSecurity #InfoSec

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.32.5 is out — a report-quality + routing-integrity release. A compliance report is only as good as its “why this violates” paragraph, so this cycle sharpens exactly that: the prose, the JSON artifact, and the guards behind them. 🧵

[NSAuditor AI @Nsasoft]

Two things most teams don't realize about Amazon RDS 👇

A database you deleted can leave an unencrypted copy of its data behind. And RDS Proxy ships accepting unencrypted connections by default.

NSAuditor AI EE 0.32.4 closes both blind spots — and a third, subtler one. 🧵

[NSAuditor AI @Nsasoft]

NSAuditor AI Enterprise 0.32.2 is live.

The GRC connector line-up is now a complete trio: Vanta, Drata, and — new — Secureframe. Each pushes your compliance-scan evidence to your GRC platform at scan time, opt-in, at the same early-access shape. 🧵

[NSAuditor AI @Nsasoft]

An auditor should never see your engineering shorthand.

NSAuditor AI EE 0.32.1 ships a cleaner Report on Compliance: the "Why this violates" evidence on every control, across all 7 frameworks, is now free of internal engineering notes. 🧵

[NSAuditor AI @Nsasoft]

Ask for three clouds, get three clouds.

`nsauditor-ai scan --host aws,gcp,azure` now audits every cloud you name — or stops with a clear error. What can no longer happen: a cloud reported "audited, clean" when the scanner never made a single API call to it.

NSAuditor AI CE 0.2.24 + EE 0.31.10 🧵

[Boris Cherny @bcherny]

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:

1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales

Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.

A healthy team needs a mix of these, depending on the product:

- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2

Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

[NSAuditor AI @Nsasoft]

NSAuditor AI CE 0.2.23 + Enterprise 0.31.9 are live.

A router scan should audit the router — not three cloud accounts because their credentials happen to be in the environment. This release makes --host the single signal for what actually gets scanned. 🧵

[NSAuditor AI @Nsasoft]

A single piece of positive compliance evidence shouldn't speak the same language to every auditor.

NSAuditor AI EE 0.31.8 makes one RDS audit-log-retention finding cite PCI DSS Req 10.5.1 on the PCI report — and say nothing PCI-specific on SOC 2. 🧵

[NSAuditor AI @Nsasoft]

That finding routes to two places at once: PCI DSS 10.5.1 and, via the cross-framework inheritance anchor, SOC 2 CC7.2.

A neutral caveat is right for SOC 2 but strips the citation a PCI assessor actually wants. 0.31.8 adds a per-framework caveat override.

[NSAuditor AI @Nsasoft]

A compliance scanner's worst failure isn't a false alarm — it's a green checkmark over a database that's logging nothing at all.

NSAuditor AI EE 0.31.7 closes exactly that on the AWS RDS audit-logging surface. 🧵

[Nsasoft @NsasoftUS]

@CryptoTweets The review of Nsauditor AI Enterprise by Zhipu is very interesting:

[NSAuditor AI @Nsasoft]

Everyone's calling Zhipu's GLM-5.2 the next "DeepSeek moment" in AI.

So we handed it the full NSAuditor AI Enterprise architecture and asked it to tear the thing apart.

Here's what it said. 🧵

[NSAuditor AI @Nsasoft]

Everyone's calling Zhipu's GLM-5.2 the next "DeepSeek moment" in AI.

So we handed it the full NSAuditor AI Enterprise architecture and asked it to tear the thing apart.

Here's what it said. 🧵

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.31.6 is live.

A cloud audit is only as honest as its coverage. When an AWS account holds more snapshots, databases, or log groups than a single enumeration pass returns, the un-enumerated tail used to read clean.

Not anymore — it now fails closed. 🧵

[Nsasoft @NsasoftUS]

@jaydee_757 "If you think $5 XRP is the top/maximum, you don't understand the market we are targeting" - Brad Garlinghouse

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.31.5 closes a backup-shaped false-clean.

A database snapshot is a complete, restorable copy of your data — an attacker who can read or restore one bypasses every control on the live database. 0.31.5 closes the last two gaps in that audit surface.

🧵

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.31.4 is live.

A cloud scan with real misconfigurations no longer shows the network summary “Host is UP — No open services detected” at the report surface. The cloud conclusion now leads with findings by severity + the top risks.

Detection unchanged. 🧵

[NSAuditor AI @Nsasoft]

NSAuditor AI EE 0.31.3 is out.

The most dangerous false-clean is the one that hides in a failed enumeration: a scanner that can't even list a resource population, then blesses it as clean. 0.31.3 makes that impossible across 12 AWS plugins. 🧵