Idea Details

Forced log of changes without the need of the developer saving changes

Last activity 7 days ago
Gleydson Ferreira Neves's profile image
01-12-2021 10:11

Developers can open, edit and run codes with stage logging disabled in debug mode and leave no traceability. In development environment, this does not represent any risks, but in environments connected with live data as pre-prod or as emergency environment as it is called where I work, this represents a risk.
A developer can open a code, edit it to her/his will, execute in debug mode with logging disabled, then close the code without saving. The described steps would allow a developer to influence a process outcome with live data with no traceability, and that should be seen as a vulnerability of the application even though it can be prevented via administrative procedures and privileges limitations, but Blue Prism itself states to expose the code to live data for final adjustments before going fully live, where people will understand that it is "ok" to have live data and a developer making final adjustments.
Organizations acknowledging this risk, will resort to administrative efforts to cover it as applying 4-eyes principle for interventions that includes live data, but then, if there was a way to create this guarantee of traceability, it wouldn't prevent the impact, but it would enable organizations to find out who was responsible for such actions, and as it would be in place, would be one less reason for someone to think about creating harm.

The idea is: create a way to force changes to be logged in the Blue Prism instance/environment, independent from developer action of saving her/his changes.

Ideas Portal

• If you like this idea – vote! Ideas with a higher score are more likely to be supported by the product review teams.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Community collaboration is key!
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, an idea is open for voting and comments to further the discussion around this idea.
This idea already exists! A change to the Duplicate status will always include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will always be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
Coming Soon!
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Coming Soon! status are not attached to a binding timeline, but there is a concrete plan to implement this idea. Therefore we will have status does not allow for voting.
Congrats! Your idea has been accepted by the team and is now in production! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!