<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Nasugn NDMS — Blog</title><description>Document management for regulated teams: tenant isolation, retention &amp; disposition, e-signatures, and records you can defend.</description><link>https://d3ck6wetgcewte.cloudfront.net/</link><language>en</language><item><title>E-signatures you can defend: sealed, audited, and part of the record</title><link>https://d3ck6wetgcewte.cloudfront.net/blog/e-signatures-you-can-defend/</link><guid isPermaLink="true">https://d3ck6wetgcewte.cloudfront.net/blog/e-signatures-you-can-defend/</guid><description>Getting a document signed is easy. Being able to prove who signed what, when, and that it hasn&apos;t changed since is the hard part. Here&apos;s how e-signatures work when they live inside your document system.</description><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate><category>e-signatures</category><category>contracts</category><category>audit trail</category><category>documents</category><category>compliance</category></item><item><title>Multi-tenant isolation: a WHERE clause is not a security boundary</title><link>https://d3ck6wetgcewte.cloudfront.net/blog/multi-tenant-isolation-where-clause/</link><guid isPermaLink="true">https://d3ck6wetgcewte.cloudfront.net/blog/multi-tenant-isolation-where-clause/</guid><description>In multi-tenant SaaS, the difference between one customer&apos;s data and another&apos;s often comes down to a filter in application code. Here&apos;s why that&apos;s fragile — and how row-level security makes isolation something the database enforces.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate><category>multi-tenancy</category><category>row-level security</category><category>postgres</category><category>security</category><category>isolation</category></item><item><title>What &apos;automated retention&apos; really means for your documents</title><link>https://d3ck6wetgcewte.cloudfront.net/blog/what-automated-retention-really-means/</link><guid isPermaLink="true">https://d3ck6wetgcewte.cloudfront.net/blog/what-automated-retention-really-means/</guid><description>Keeping records &apos;for seven years&apos; is a policy. Actually archiving, locking and disposing of them on schedule is engineering. Here&apos;s how automated retention and disposition works in a document system built for it.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><category>retention</category><category>records management</category><category>disposition</category><category>compliance</category><category>WORM</category></item></channel></rss>