I'm writing SEC complaint (section 17-a4) data protection file system application which needs to write protect the file till the protection expires. Before allowing modification on a file/directory, the application needs to determine the correct current time which is tolerant to altered system time, fake NTP servers, man-in-middle attacks when reading time from secured NTP servers or other general threats. The system won't be SEC compliant as someone can alter the system clock to make the protected file look expired and then deleting it.
So far, I have thought about generating quorum after reading from various secure NTP servers. Other approach is to use own implementation of compliance clock which can't be modified by anyone. The downside of this approach is that such clock won't be reliable across geo-distributed nodes.
I wish someone could help me knowing about prior work done on this problem or other approaches, thank you.