# PNT RMMS -- security contact # https://rmms.pronovatech.com # # Format: RFC 9116. Fields are "Name: value"; lines starting with "#" are # comments. Served from /.well-known/security.txt as text/plain. # # ASCII ONLY, DELIBERATELY. This file is served with "Content-Type: text/plain" # and no charset parameter (that is what the .NET static-asset endpoint emits # for .txt -- verified in obj/.../staticwebassets.build.endpoints.json), and a # client that assumes ISO-8859-1 would mangle any non-ASCII byte. Keeping the # file to ASCII makes the missing charset harmless. Do not "prettify" the rules # below into box-drawing characters. # # --------------------------------------------------------------------------- # THIS FILE EXPIRES. Expires below is a REQUIRED field and the expiry is # enforced by the spec, not by us: a researcher's tooling treats an expired # security.txt as stale and is entitled to disregard everything in it. A lapsed # file is worse than no file, because it advertises a reporting channel and then # withdraws the assurance that anyone is reading it. # # HOW IT GETS RENEWED -- not by anyone remembering. tests/PNT.Tests/ # w41SecurityContactTests.cs contains SecurityTxt_Expires_IsNotWithinRenewalWindow, # which FAILS the build 30 days before the date below. That is the alarm. When it # goes red the renewal is two edits: # 1. Move Expires forward, keeping it under one year out (RFC 9116 section # 2.5.5 advises less than a year). # 2. Re-confirm every Contact below still reaches a monitored human. An address # that bounces is the exact failure this file exists to prevent. # Do not silence the test by widening its window -- that removes the only alarm. # # CONTACT ADDRESS -- READ BEFORE CHANGING. support@pronovatech.com is used here # because it is an address this site already publishes and monitors (/privacy # section 10, /terms, /gdpr, /about). A dedicated security@pronovatech.com alias # is the better end state and is a pending owner action; when that mailbox # exists, add it as the FIRST Contact line -- RFC 9116 section 2.5.3 makes # Contact order a preference order -- and keep support@ below it as the fallback. # # NO Encryption: FIELD, deliberately. We do not operate an OpenPGP key for this # address. Publishing a key whose private half nobody holds would be a worse # claim than the omission. # # NO Acknowledgments: or Hiring: FIELD. Both are optional and we have no page to # point either at. # --------------------------------------------------------------------------- Contact: mailto:support@pronovatech.com Contact: https://rmms.pronovatech.com/security Policy: https://rmms.pronovatech.com/security Preferred-Languages: en Canonical: https://rmms.pronovatech.com/.well-known/security.txt Expires: 2027-02-19T23:59:59.000Z