Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

John O. Neilson

dblp:96/6865 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1984
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Security and privacy · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Operating systems · 100%
Network and information security
1 paper
Systems and software security · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems › system security › operating system security › secure operating system
multilevel secure operating system
0.011984
Design Experiences from the Multilevel Secure MCF Operating System · S&P 1984
Operating systems › system security › operating system security
secure operating system
0.011984
Design Experiences from the Multilevel Secure MCF Operating System · S&P 1984
Systems and software security
multilevel security
0.011984
Design Experiences from the Multilevel Secure MCF Operating System · S&P 1984
YearPublicationVenuePosition
1984 Design Experiences from the Multilevel Secure MCF Operating System
abstract
The multilevel secure Military Computer Family Operating System program will provide a new high-water mark for multilevel security design and definition. The operating sys-tem will be the first verified Ada* program, and will be a fielded multilevel secure operating system. The operating system is being built for a new machine that has significant architectural features for security. This paper reveals some of the experiences and problems encountered by the RCA team during the concept definition phase of the program, and describes some of the obvious and not-so-obvious pitfalls of designing a product multilevel secure operating system. Many of the problems have been mitigated by advances in the definitions and criteria for multilevel security, and one of the goals of this paper is to help eliminate or mitigate the problems for the next system to be built.
John O. Neilson, F. E. Wuebker
S&P1