pub enum SecurityEvent {
Show 20 variants
FirmwareUpdated,
FailedToAuthenticateAtCsms,
CsmsFailedToAuthenticate,
SettingSystemTime,
StartupOfTheDevice,
ResetOrReboot,
SecurityLogWasCleared,
ReconfigurationOfSecurityParameters,
MemoryExhaustion,
InvalidMessages,
AttemptedReplayAttacks,
TamperDetectionActivated,
InvalidFirmwareSignature,
InvalidFirmwareSigningCertificate,
InvalidCsmsCertificate,
InvalidChargePointCertificate,
InvalidTLSVersion,
InvalidTLSCipherSuite,
MaintenanceLoginAccepted,
MaintenanceLoginFailed,
}Expand description
Standardized SecurityEventNotification.type values, from the 1.6 Security Whitepaper.
A closed set: it holds only the values the specification
defines. The wire field is a string, so a deployment can still
send something else – from_wire returns None for that,
which is not by itself a protocol error.
Variants§
FirmwareUpdated
The Charge Point firmware is updated
FailedToAuthenticateAtCsms
The authentication credentials provided by the Charge Point were rejected by the Central System
CsmsFailedToAuthenticate
The authentication credentials provided by the Central System were rejected by the Charge Point
SettingSystemTime
The system time on the Charge Point was changed
StartupOfTheDevice
The Charge Point has booted
ResetOrReboot
The Charge Point was rebooted or reset
SecurityLogWasCleared
The security log was cleared
ReconfigurationOfSecurityParameters
Security parameters, such as keys or the security profile used, were changed
MemoryExhaustion
The Flash or RAM memory of the Charge Point is getting full
InvalidMessages
The Charge Point has received messages that are not valid OCPP messages, if signed messages, signage invalid/incorrect
AttemptedReplayAttacks
The Charge Point has received a replayed message (other than the Central System trying to resend a message because there was for example a network problem)
TamperDetectionActivated
The physical tamper detection sensor was triggered
InvalidFirmwareSignature
The firmware signature is not valid
InvalidFirmwareSigningCertificate
The certificate used to verify the firmware signature is not valid
InvalidCsmsCertificate
The certificate that the Central System uses was not valid or could not be verified
InvalidChargePointCertificate
The certificate sent to the Charge Point using the CertificateSigned.req message is not a valid certificate
InvalidTLSVersion
The TLS version used by the Central System is lower than 1.2 and is not allowed by the security specification
InvalidTLSCipherSuite
The Central System did only allow connections using TLS cipher suites that are not allowed by the security specification
MaintenanceLoginAccepted
Successful login to the local maintenance interface. It is recommended to include information like the user identification and the origin of the login attempt in the techInfo field
MaintenanceLoginFailed
Failed login attempt to the local maintenance interface. It is recommended to include information like the user identification and the origin of the login attempt in the techInfo field
Implementations§
Source§impl SecurityEvent
impl SecurityEvent
Sourcepub const ALL: &'static [Self]
pub const ALL: &'static [Self]
Every value this version’s specification defines (20), in spec order.
Sourcepub fn from_wire(value: &str) -> Option<Self>
pub fn from_wire(value: &str) -> Option<Self>
Parses a wire value, returning None for values the
specification doesn’t define (e.g. a vendor’s own).
Sourcepub const fn is_critical(&self) -> bool
pub const fn is_critical(&self) -> bool
Whether the Security Whitepaper marks this event critical, meaning it must be reported to the Central System even when not explicitly monitored.
Trait Implementations§
Source§impl Clone for SecurityEvent
impl Clone for SecurityEvent
Source§fn clone(&self) -> SecurityEvent
fn clone(&self) -> SecurityEvent
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more