Offline SMPS protection functions done only in software?

[Flyback]

Ive always done offline Flyback SMPS up to 75W with output overload protection (hiccup mode or latched shutdown) , output short circuit protection and output overvoltage protection implemented in hardware.
However, is it acceptable (from a regulations viewpoint) to implement these protections only in software, with say a microcontroller?
What I mean is, having a microcontroller on the secondary side of the main flyback, being powered from an extra, smaller “housekeeping” offline flyback power supply. –This microcontroller then observes for the faults mentioned and shuts down the main flyback if any of these faults occur.
Is this OK from the regulations viewpoint?

 

[ronsimpson]

Is this OK from the regulations viewpoint?

Ask the regulators.

I think they don't care how you do your job. Thy do require the supply to work safely.

 

[Flyback]

thanks anyway, but as you know, the regulators charge big money for questions, and its just not possible to keep asking them for every issue that comes up.