The System360 Model 20 Wasn't As Bad As All That 3872

different operating systems were structured in different ways ... most of the "batch" systems tended to have minimal security, in part because there was little direct access to the actual machine by the people using them.

the time-sharing systems

tended to have somewhat more robust security ... and, in fact, saw some uses in organizations that tended to have somewhat stringent. this has a reference to some use from the late 60s and early 70s:

I've repeated several times the effort at the science center

where the "unannounced" 370 virtual memory was emulated on the science center's 360-67. this had some number of issues since the corporation treated the unannounced 370 virtual memory as extremely sensitive corporate information ... and the science center's 360-67 was also providing online service to a number of non-employees in the boston area, including some number of students from various boston area insbreastutes of higher education (bu, mit, harvard, etc).

another activity was that in the initial port apl-360 to cms-apl on the cambridge system, it opened up the APL workspace size from something like 32kbytes (real) to several megabytes (virtual). the corporate hdqtrs people found it attractive for doing business modeling and had the absolutely most sensitive of all corporate information loaded on the cambridge machine so they could do business modeling remotely from corporate hdqtrs. Being able to provide the highest level of data protection was a real issue ... especially with all the non-employee and student access to the same machine concurrently.

misc. past posts mentioning the effort virtualizing unannounced 370 virtual memory ... which was also one of the first distributed development projects using the internal network (between cambridge and endicott) ... and of course the cambridge host name was cambrdige:

past posts mentioning the internal network