Comments by "Deborah Freedman" (@deborahfreedman333) on "This is how authorities were able to identify the Pentagon leak suspect" video.
-
When I was a young programmer, working for a bank, we had to check out modules, in order to change the code. You had to write external and internal specifications, and in those specifications, note which modules you'd need access to. Whenever you checked out a module, you had to note the SR# or TR# (service request or trouble report), and the external specs needed to state a need for that module, and have been approved. As I was working in Realtime programming, I could only access assembly language modules. Programmers, writing COBOL, were not allowed access to our modules. Sure, we all had specific security clearances, but we also had to demonstrate a need for each module. Of course, there was all sorts of regression testing, before we could check the modified module back in. But, the main thing was, access was specific to need. Even the security guys were not allowed to touch our code, because they were not qualified to understand assembly language. When I was working on communication protocol changes, I could only access the input and output modules, of other departments. If this guy was only maintaining IT, why was he given access to areas that didn't have written trouble reports?
13
-
3
-
2
-
2
-
1
-
1
-
1