Why can't we prevent a datareader to either saturate an entity or load into a saturated entity ?

Mateo DE LOS RIOS
Mateo DE LOS RIOS Active Partner
Second Anniversary First Comment 5 Up Votes
edited February 2021 in Platform

Hello Community,

What a good surprise this morning when i saw that an entity in my application was saturated !



image




Even better surprise, when no alert was displayed in the web client !!!






Even better surprise, when i saw that a datareader that  was running at 3:45 AM and has saturated the entity !
Even better surprise, when no log was generated, and when i saw that the datareader don't even stop or alert that an entity is saturated !





And best surprise, the data loaded by the datareader has an increased target index by 1 on an other axis in the Datareader  !

Result : In my HR application, i have employees whose their Cost center has shifted due to the saturation. In an application where the security is critical, thoses employees salaries were readable by users who shouldn't be able to.

My Datareader, because of the saturation, has just ruined the security. And not a single alert. Not a single to way to prevent datareader to stop if an entity is about to be saturated.

How is that even possible? How can i explain that to my customer ?


------------------------------
Mateo DE LOS RIOS
Consultant
Micropole Group
France
------------------------------

Answers

Categories