A municipal payments topic carries fee and refund events that many microservices can see on the shared bus. What security basic should the platform enforce?
Select an answer to reveal the explanation.
Short Explanation
The payments bus is not a bulletin board for every city app. Lock who can write and who can read that topic—like badge access to a cash room. Shared messaging still needs authorization, not open-mic publishing.
Full Explanation
Kafka-style buses are shared infrastructure; topic-level authentication and authorization limit which services may produce or consume sensitive streams. Default-open access, firewall-only thinking, or clear-text convenience undermine payment-event confidentiality and integrity. Civic platforms should grant least-privilege publish/subscribe rights on topics such as payments and pair them with encryption and audit where policy requires. Security on the bus is part of ingestion design, not an afterthought.