Proyecto: Relational Cybersecurity: When Security Emerges Without Walls - anfelacer/Relational-Cybersecurity-When-Security-Emerges-Without-Walls GitHub Wiki
Relational Cybersecurity: When Security Emerges Without Walls
Relational Cybersecurity redefines security beyond walls. Instead of hiding data, it establishes responsibility for what happens when access occurs. Security emerges from openness, care, and accountable relationships.
Conceptual system design, ethical-by-design architecture, relational access logging, accountability rules, blockchain-based immutable records (exploratory), open data governance frameworks.
Inspiration
This project is inspired by lived experience of openness as a condition for care, dignity, and survival.
Across history, the greatest conflicts have not emerged from what exists, but from what is hidden. As in The Lord of the Rings, the problem is not the ring itself, but the decision to conceal it. Opacity creates fear, speculation, and violence, while openness reveals reality and demands responsibility.
In digital security, so-called “transparency” has become a trap. It promises clarity while preserving deep asymmetries: some see, others do not. Walls are built to protect systems, markets, and power structures, not the people behind the data. This project emerges from questioning that logic and asking a different question: what if security did not begin with hiding, but with care?
What it does
Relational Cybersecurity proposes removing the wall as the core mechanism of security.
Instead of focusing on who is allowed to access information, the system focuses on what happens when access occurs. Every access is recognized, logged, and tied to explicit responsibility. Data is treated not as a neutral asset, but as a living extension of someone.
Security emerges from openness, situated relationships, and accountable agreements, not from blind spots created by concealment.
How we built it
This project was built as a conceptual and technical framework grounded in ethical-by-design principles.
The architecture prioritizes:
- Openness over opacity
- Responsibility over control
- Traceability over blind trust
The system design explores relational access logs, accountability rules, and the possibility of integrating immutable records (such as blockchain-based traces) to ensure that access always implies care, not ownership.
Relational access in practice (lived scenarios)
This framework is grounded in real-world scenarios where openness enabled care precisely because access was recognized, not hidden.
In shared digital environments with full access, the ability to see, move, group, and reorganize information allowed responsible intervention. Openness made it possible to understand the whole system, assume responsibility for actions, and prevent silent loss or abuse. Care emerged because access was visible and actionable.
In contrast, when information was accessed without recognition or ethical license, harm occurred—not because access existed, but because responsibility was removed. The absence of acknowledgment created a blind spot where care could not be demanded.
This logic also applies beyond digital systems. In professional and ethical governance contexts, voluntary recognition of sensitive realities enabled meaningful intervention. When access and visibility were explicit, systems could respond with care rather than punishment. When openness existed, responsibility became possible.
These scenarios demonstrate that security does not fail because people access information. It fails when access is detached from recognition, accountability, and ethical responsibility.
Challenges we ran into
The main challenge was resisting the dominant assumption that security equals restriction.
Most security models are built around fear of access. Challenging this assumption required reframing security as a relational process rather than a technical barrier. Translating lived, embodied knowledge of vulnerability into a language legible for technical systems and hackathon formats was also a significant challenge.
Accomplishments that we're proud of
We are proud of articulating a coherent alternative to wall-based security models.
This project successfully reframes cybersecurity as a practice of care, responsibility, and parity, making visible the political and human dimensions that are usually hidden behind technical jargon.
What we learned
We learned that security is not primarily a technical problem, but a relational one.
Blind spots are not accidental; they are designed. When the wall disappears, excuses disappear as well. Responsibility becomes visible, and care becomes unavoidable.
What's next for Relational Cybersecurity When Security Emerges Without Walls
Next steps include developing functional prototypes, defining governance rules for relational access, and testing this framework in real-world contexts involving vulnerable populations and shared digital infrastructures.
The long-term vision is to contribute to a shift in how security, value, and trust are designed in digital systems.
This project is grounded in the understanding that autonomy, when recognized and recorded, is not a threat to security but its strongest guarantee.
This project is grounded in the understanding that autonomy, when recognized and recorded, is not a threat to security but its strongest guarantee. This framework can operate across healthcare, ethical governance, and value systems, wherever access to sensitive information requires responsibility rather than control.
Cómo lo construimos
Este proyecto se construyó desde la apertura como práctica real, no como ideal abstracto.
Parte de la experiencia directa de habitar sistemas abiertos donde el acceso amplio permitió el cuidado, la reorganización responsable de la información y la intervención oportuna. En estos contextos, el acceso no fue una amenaza, sino una condición para asumir responsabilidad.
El diseño del marco reconoce que:
- El acceso siempre ocurre
- El daño aparece cuando el acceso no es reconocido
- La responsabilidad solo es posible cuando existe registro y licencia ética de cuidado
A nivel técnico, la arquitectura propone:
- Registros explícitos de acceso entendidos como reconocimiento, no como vigilancia
- Licencias éticas de cuidado asociadas al acceso a la información
- Trazabilidad posterior como condición para la intervención y la reparación
- La posible integración de registros inmutables (por ejemplo, mediante blockchain) para evitar puntos ciegos estructurales
La seguridad no se construye evitando que alguien entre, sino garantizando que, si entra, exista una relación clara entre acceso, acción y responsabilidad.
Este proyecto parte del reconocimiento de que la autonomía, cuando es reconocida y registrada, no es una amenaza para la seguridad, sino su garantía más sólida.
Este proyecto parte del reconocimiento de que la autonomía, cuando es reconocida y registrada, no es una amenaza para la seguridad, sino su garantía más sólida. Este enfoque puede operar en salud, gobernanza ética y sistemas de valor, allí donde el acceso a información sensible requiere cuidado y responsabilidad, no control.
🧭 Un diagrama del sistema (1 imagen)
Un solo diagrama que muestre:
Usuario A accede Registro de acceso (no muro) Licencia ética Acción Responsabilidad posterior
[Access] → [Recognition Log] → [Ethical License] → [Action] → [Accountability]
Access ↓ Recognition (who / why) ↓ Ethical Care License ↓ Action ↓ Accountability / Repair