Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • 13
    Code reviews? Security audits? Educating your developers in security? Commented May 12, 2019 at 7:00
  • "they want to prevent unwanted fields to be returned by API system." Why? Is this for performance reasons, data compliance reasons, or something else? Is it actually the biggest problem you need to fix right now? Commented May 12, 2019 at 7:03
  • 3
    Do your developers actually want to create a secure application that doesn't leak unwanted information? If yes, then provide trainings and materials that explain what information is secure. If not, then you have much worse problem than leaking data. Commented May 12, 2019 at 7:07
  • 6
    I sense a power struggle in this question between database administrators on the one hand and application developers on the other hand. And a frustrated response from a representative of the first group. "We DBAs smart, them developers stupid!" Commented May 12, 2019 at 7:14
  • en.wikipedia.org/wiki/Polyinstantiation Commented May 13, 2019 at 14:48